unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
* [DRAFT] Improve reporting of exception locations
@ 2022-10-12  6:35 Andrew Whatson
  2022-10-12  6:42 ` Andrew Whatson
  2022-10-12 19:16 ` Maxime Devos
  0 siblings, 2 replies; 3+ messages in thread
From: Andrew Whatson @ 2022-10-12  6:35 UTC (permalink / raw)
  To: guile-devel

Hello guile-dev!

I'm working on a revised patch to improve the reporting of exception
locations, after last month's initial flawed attempt.

The new patch takes the more radical approach of capturing the stack
when an exception is created, including it as part of the compound
exception object.  This should ensure that we capture a correctly
trimmed stack, while avoiding the complexities of pre-unwind handlers.
This is similar to other dynamic languages where it's common to bundle
stack info with exception objects.

This approach will probably have a negative impact on code which is
sensitive to the performance of exception creation; capturing the
stack is more expensive than NOT capturing it.  Is this something that
we need to be concerned about?

I'm still working on integrating these changes into Guile, but thought
it's worth getting early feedback on this one.

Patch to follow!

Cheers,
Andrew



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-10-12 19:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-12  6:35 [DRAFT] Improve reporting of exception locations Andrew Whatson
2022-10-12  6:42 ` Andrew Whatson
2022-10-12 19:16 ` Maxime Devos

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).