Pthread_exit(NULL) segfaults?

Try using valgrind (specifically the "memcheck" part). It can quickly help you to pinpoint invalid memory accesses at runtime, sometimes even including runs of your program that do not crash.

I suspect it's a combination of all of these, but the problem went away. It only happened when I typed 'quit' too soon after the program started, but I don't have time to properly debug this now and the assignment is due already anyway. @John - I actually was setting up valgrind for just this purpose.

EDIT I ran it earlier and it didn't help me with this problem, but I definitely found some memory I wasn't freeing /EDIT Everybody else - I think you're right, it's probably some sort of memory corruption. @caf - I forgot to check other thread... but I was seeing the problem in both threads. GDB was pointing me at the one that was actually segfaulting.

EDIT I checked the other threads and it was either waiting on the pt_join (if the segfault was with the pt_exit) or somewhere just before the pt_exit (if the segfault was in the pt_join) /EDIT.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.