Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backtraces could print all the arguments to all the routines #5054

Open
p6rt opened this issue Jan 15, 2016 · 5 comments
Open

backtraces could print all the arguments to all the routines #5054

p6rt opened this issue Jan 15, 2016 · 5 comments
Labels
LTA Less Than Awesome; typically an error message that could be better

Comments

@p6rt
Copy link

p6rt commented Jan 15, 2016

Migrated from rt.perl.org#127282 (status was 'open')

Searchable as RT127282$

@p6rt
Copy link
Author

p6rt commented Jan 15, 2016

From @AlexDaniel

This bug report is a continuation of
https://rt-archive.perl.org/perl6/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).

@p6rt
Copy link
Author

p6rt commented Jan 16, 2016

From @hoelzro

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​:

This bug report is a continuation of
https://rt-archive.perl.org/perl6/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).

@p6rt
Copy link
Author

p6rt commented Jan 16, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Jan 17, 2016

From @jnthn

On Fri Jan 15 11​:56​:17 2016, alex.jakimenko@​gmail.com wrote​:

This bug report is a continuation of
https://rt-archive.perl.org/perl6/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.

@p6rt
Copy link
Author

p6rt commented Oct 7, 2017

From @AlexDaniel

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​:

On Fri Jan 15 11​:56​:17 2016, alex.jakimenko@​gmail.com wrote​:

This bug report is a continuation of
https://rt-archive.perl.org/perl6/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.

@p6rt p6rt added the LTA Less Than Awesome; typically an error message that could be better label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LTA Less Than Awesome; typically an error message that could be better
Projects
None yet
Development

No branches or pull requests

1 participant