[Bug c++/60959] New: Does “cout(char*)NULL” doing “close(1)” ?

2014-04-24 Thread sree.gooogle at gmail dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: sree.gooogle at gmail dot com In the following piece of C++ code I have used cout(char*)NULL; after this line, my program printing nothing to the output screen. Does it mean I have done close(1) with cout here? #includeiostream

[Bug c++/60959] Does “cout(char*)NULL” doing “close(1)” ?

2014-04-24 Thread sree.gooogle at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60959 --- Comment #2 from Sreenath U S sree.gooogle at gmail dot com --- sets the badbit on the stream which causes nothing to be printed after that.; So this is a defined behavior or it varies on compiler to compiler?

[Bug c++/60959] Does “cout(char*)NULL” doing “close(1)” ?

2014-04-24 Thread sree.gooogle at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60959 --- Comment #4 from Sreenath U S sree.gooogle at gmail dot com --- Okay Thanks. One more thing, Is there any way to make the remaining cout statements to get printed in gcc without removing the faulty cout(char*)NULL;?

[Bug c/60388] New: Program received signal SIGSEGV, Segmentation fault. 0xb7fb62ff in __pthread_create_2_1

2014-03-02 Thread sree.gooogle at gmail dot com
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sree.gooogle at gmail dot com Created attachment 32242 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32242action=edit c program used for Segmentation fault at line

[Bug c/60388] Program received signal SIGSEGV, Segmentation fault. 0xb7fb62ff in __pthread_create_2_1

2014-03-02 Thread sree.gooogle at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60388 Sreenath U S sree.gooogle at gmail dot com changed: What|Removed |Added Keywords||diagnostic