Re: Should crash be the top of ex.err?
- Posted by mattlewis (admin) Feb 03, 2015
- 1411 views
dcuny said...
Bump
So are there any objections to the crash() message be placed at the top of the list without altering the stack trace, as in my prior suggestion?
Here's a workaround for you: Use error:crash() instead of just crash(). For reasons (it's been a while, so I don't recall, exactly) the first gets inlined while the second doesn't. So the inlined version doesn't have crash() in the stack trace.
This is probably a bad thing, as it confuses error reporting on inlined routines, but I'm not sure if there's an easy / good way to keep inlined stuff in stack traces. They should, of course, be pretty small, so there's not a whole lot of places for an error to hide, but it can be misleading.
Matt
