develooper Front page | perl.perl5.porters | Postings from January 2022

Broken stack traces from use statements.

Thread Next
January 13, 2022 05:04
Broken stack traces from use statements.
Message ID:
This subject has come up multiple times and is a source of deep frustration
for me, and deep confusion for the many non-perl developers who work on
perl code at

This was fixed by Dave Mitchell in f2f32cd638746f538da6db804dab6dd54e654f30

This patch was then reverted in merge
commit c0d05305c156c83e4f9f3a207451b3175fbb7f24.

Thus stack traces are *still* broken. I am looking at many examples right
now and it is impossible to debug what is happening. I cannot post the work
examples but the patch referenced includes examples from its tests.

Can we please fix this once and for all? We are running patched perl's at
work so that we can fix this (without any sign of any related fallout!),
and every time we release a new perl we have to reapply
f2f32cd638746f538da6db804dab6dd54e654f30. When the people who build new
perls forget then we end up with mass confusion amongst our devs.

Perl has a really bad name amongst the devs we hire, this one of the
reasons. Can we please please please FINALLY DO SOMETHING about this? Perl
has so many weird ways to establish a dependency and this bug makes it
almost impossible to debug non-trivial cases even for an expert class perl
dev like myself.

I beg of you, do not let another perl get released with this bug in place!


perl -Mre=debug -e "/just|another|perl|hacker/"

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