News for hackers. Stuff that matters.

A comment on Why bad scientific code beats code following "best practices". Parent comment

Re:Why bad scientific code beats code following "best practi... by apw on Monday May 12, 2014 @09:10PM (#7736193)
It's not clear that a nicely formatted error message is preferable to a core dump.

With a core dump one can explore the execution environment at the time of the crash.

A nice compromise is a macro that prints an error message and then calls __builtin_trap().

[ Parent | on HN ]
Re:Why bad scientific code beats code following "best practi... by afarrell on Tuesday May 13, 2014 @12:21PM (#7738932)
But a nicely formatted error message, so long as it is correct, can be read by many more people than a core dump.

I don't know how I would read a core dump of an error in a python program to understand where an exception came from.

[ Parent | on HN ]