Discussion Locked

Threads exiting and leaving parent zomb

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have ran into a conditon where I have a mutlithreaded application running on Linux and my parent thread is left as a zombie. The thread that exited left a core, but the core does not help as to what actually occured through GDB...

Any suggestions?

2 replies

by jaqui

core contains no usefull data, then you forgot 2 small things:
1) not debug enabled build when compiled
2) no error messages in every decision to help pinpoint where the errors are.

try adding --debug=all to the build instructions in the makefile.
or else, using the preprocessor to enable a debug build through the configure script or a release build.
./configure --debug(N) is usually the option, though check as your configure script may not have it.

by solrak29

Thanks, but I have the fundamentals, and have a debug version running. What I mean about the core is that it doesn't tell me anything obviois (i.e. null pointer, exception). I do get a stack, somewhere in the ostreamstream...

Thanks

This discussion is closed to new replies.