search

hossbeast / fab

build optimally
GNU General Public License v3.0
4 stars 0 forks source link

error reporting - do not unwind entire call stack by default #24

Closed hossbeast closed 11 years ago

hossbeast commented 11 years ago

In a normal build of fab, error reporting should only report the immediate frame of the error.

unwinding and reporting on the entire callstack should be the default in DEVEL-compiled mode.

hossbeast commented 11 years ago

Done. A development build now has

--errors-unwind --errors-immediate

A non-development build doesn't have the option, and defaults to --errors-immediate.

This required reimplementing the calling convention across the entire codebase (including liblistwise) such that 0 means success, nonzero means failure. At present, I am using >0 to mean error + unwind, and <0 to mean error (but dont unwind). That's how I should have implemented the calling convention anyway though.