develooper Front page | perl.perl5.porters | Postings from September 2023

Re: Native stack traces?

Thread Previous | Thread Next
Christian Walde
September 8, 2023 12:54
Re: Native stack traces?
Message ID:
On Fri, 08 Sep 2023 12:56:00 +0200, Dave Mitchell <> wrote:

> On Fri, Sep 08, 2023 at 12:24:58PM +0200, Ovid wrote:
>> I don't know if a native stack trace implemented in the Perl core would
>> solve the problems, but if we were to add "official" stack traces in the
>> core, allowing people to pass a callback or frame subclass for filtering, I
>> think this would be a benefit.
>> If we later want to add a native exception system, native stack traces
>> would likely be a prerequisite.
> I'm not really sure in this context what you consider to be a "native"
> stack trace which isn't already provided by perl?
> Carp and Devel::StackTrace are just wrappers of varying heaviness around
> perl's built-in call stack introspection facility: caller() and @DB::args.
> ...
> What else would you want perl to natively provide?

i think what ovid is getting at that there could be value in moderately configurable stacktrace generators implemented in the perl c core, with the hope that those could be considerably faster than the only current way of getting the data out of the internals, then munging it at the perl level

no idea if that would actually bear out, but that's my understanding

With regards,
Christian Walde

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About