Re: crash message in 4.0

new topic     » goto parent     » topic index » view thread      » older message » newer message
  • Posted by jimcbrown (admin) Aug 17, 2008
  • 892 views
jeremy said...
mattlewis said...

Yes, the first thing reported is crash, since that's where it happened. But the rest of the stack trace is there. If this is still unacceptable, you can call machine_proc directly, without the std/error.e wrapper.

If we were to make crash() a true built-in, it should report the correct line for the first stack trace item, right?

Jeremy

Yes, this would solve the issue quite elegantly.

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu