Skip Menu |
Report information
Id: 127282
Status: open
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: alex.jakimenko [at] gmail.com
Cc:
AdminCc:

Severity: (no value)
Tag: (no value)
Platform: (no value)
Patch Status: (no value)
VM: (no value)



To: rakudobug [...] perl.org
From: Aleks-Daniel Jakimenko-Aleksejev <alex.jakimenko [...] gmail.com>
Date: Fri, 15 Jan 2016 21:56:07 +0200
Subject: [LTA] backtraces could print all the arguments to all the routines
Download (untitled) / with headers
text/plain 523b
This bug report is a continuation of https://rt.perl.org/Ticket/Display.html?id=127281


<TimToady> while we're at it, let's make backtraces print all the arguments to all the routines...
<TimToady> well, the short ones, anyway


That would be awesome!!!

In fact, this idea was mentioned a couple of times. One of those times it was discussed whether .perl, .gist or something else should be used for the output, but unfortunately I cannot find the link (perhaps somebody else will. However, there was no final decision).

Download (untitled) / with headers
text/plain 869b
I support this idea in general, but we have to be careful if we want Perl 6 to be used in systems that support things like PCI compliance. You don't want the arguments to process-credit-card(Str $cc-num, Str $first-name, Str $last-name) to appear in logs! On 2016-01-15 11:56:17, alex.jakimenko@gmail.com wrote: Show quoted text
> This bug report is a continuation of > https://rt.perl.org/Ticket/Display.html?id=127281 > > > <TimToady> while we're at it, let's make backtraces print all the arguments > to all the routines... > <TimToady> well, the short ones, anyway > > > That would be awesome!!! > > In fact, this idea was mentioned a couple of times. One of those times it > was discussed whether .perl, .gist or something else should be used for the > output, but unfortunately I cannot find the link (perhaps somebody else > will. However, there was no final decision).
RT-Send-CC: perl6-compiler [...] perl.org
Download (untitled) / with headers
text/plain 924b
On Fri Jan 15 11:56:17 2016, alex.jakimenko@gmail.com wrote: Show quoted text
> This bug report is a continuation of > https://rt.perl.org/Ticket/Display.html?id=127281 > > > <TimToady> while we're at it, let's make backtraces print all the arguments > to all the routines... > <TimToady> well, the short ones, anyway > > > That would be awesome!!! > > In fact, this idea was mentioned a couple of times. One of those times it > was discussed whether .perl, .gist or something else should be used for the > output, but unfortunately I cannot find the link (perhaps somebody else > will. However, there was no final decision).
We'll likely only be able to support this if some kind of "debug mode" that disables optimizations is switched on. We already discard some of the info needed to do this, and we'll be getting rather more aggressive at optimization in the coming months. And performance is more pressing than this nice-to-have.
FWIW I agree about the “debug” mode.
That said, it isn't just a nice-to-have. This is something that can make people mention Perl 6 when discussing the most amazing features of modern programming languages… much like people mention grammars today :)

On 2016-01-17 04:07:19, jnthn@jnthn.net wrote:
Show quoted text
> On Fri Jan 15 11:56:17 2016, alex.jakimenko@gmail.com wrote:
> > This bug report is a continuation of
> > https://rt.perl.org/Ticket/Display.html?id=127281
> >
> >
> > <TimToady> while we're at it, let's make backtraces print all the
> > arguments
> > to all the routines...
> > <TimToady> well, the short ones, anyway
> >
> >
> > That would be awesome!!!
> >
> > In fact, this idea was mentioned a couple of times. One of those
> > times it
> > was discussed whether .perl, .gist or something else should be used
> > for the
> > output, but unfortunately I cannot find the link (perhaps somebody
> > else
> > will. However, there was no final decision).
>
> We'll likely only be able to support this if some kind of "debug mode"
> that disables optimizations is switched on. We already discard some of
> the info needed to do this, and we'll be getting rather more
> aggressive at optimization in the coming months. And performance is
> more pressing than this nice-to-have.




This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org