Brian Stark <bpstark@pacbell.net> writes:

> As for the undefined behavior that Klaus described, I would much
> rather see an error message and the program continue rather than an
> error message and the program going away. Having said that, I'll
> admit that there may be a good reason why the program goes away (I'm
> just not too familar with the libpthread internals to understand
> what is going on there).

If you get an error message but the program keeps going, you have no
way to find out where the error is. With the core dump, you can see
what happened, and have a chance of fixing it.

I think that the combination of printing messages and continuing is
not very useful - but then, I happen to think that continuing at all
isn't very useful, and only added it under duress to make it easier to
run some of the crappy code out there in the wild.

        - Nathan