-
Notifications
You must be signed in to change notification settings - Fork 556
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
warnings from while() condition are reported from wrong line #9582
Comments
From @timbunceReproduced on perl5.8.6 and v5.11.0 DEVEL34703. After executing the last statement in a while() block perl doesn't #!perl # the 'current line' is whatever line was last executed # adding a continue block avoids the problem This may seem like a minor issue but I've rated it 'high' because it has a Seems like OP_UNSTACK needs to be smarter. Naturally any solution shouldn't slow perl down. If a slowdown is unavoidable then perhaps only implement it if $^P & 0x2 Perl Info
|
From @timbunceAnother example: while ( foo() ) { his impacts stack traces and the NYTProf subroutine profiler. |
@timbunce - Status changed from 'new' to 'open' |
From @rgs2008/12/1 via RT Tim Bunce <perlbug-followup@perl.org>:
Maybe the same trick that I used in change 33710 can be used there. It Change 33710 by rgs@stcosmo on 2008/04/18 10:42:17 Fix the line-number-in-elsif longstanding bug. |
From @timbunceOn Tue, Dec 02, 2008 at 01:05:26AM -0800, Rafael Garcia-Suarez via RT wrote:
Sounds plausible. How does that actually work though? Googling that change led me to the old discussion, including some Tim. |
From @nwc10On Tue, Dec 02, 2008 at 10:56:42AM +0000, Tim Bunce wrote:
I *think* (but don't quote me on that), that: Line numbers in errors reports are calcuated by S_closest_cop() in util.c. However, something else (not sure what) must be reporting line numbers based So I infer that this is a bit of a hack to find a way of storing a line Nicholas Clark |
From @rgs2009/3/25 Nicholas Clark <nick@ccl4.org>:
Both warnings and errors go through Perl_vmess. The line number found |
From @timbunceOn Mon, Dec 01, 2008 at 03:07:42AM -0800, Tim Bunce wrote:
This is still open (and affecting NYTProf). Any chance it could be fixed for 5.12? Tim. |
From @obraOn Fri, Nov 27, 2009 at 11:03:11AM +0000, Tim Bunce wrote:
At least for now, I've added this to the blocks-5.12 list |
From @timbunceOn Fri, Nov 27, 2009 at 01:17:46PM -0500, jesse wrote:
Any news on this one? Tim. |
From @nwc10On Tue, Dec 22, 2009 at 08:09:34PM +0000, Tim Bunce wrote:
To the best of my knowledge, "no". (I think that Jesse would be the best At various times the list has been pleasantly surprised by patches appearing (I certainly don't have time) For many of the bugs, it's a skilled job to diagnose and fix them. A job. Nicholas Clark |
From @iabynOn Wed, Dec 23, 2009 at 03:16:51PM +0000, Nicholas Clark wrote:
I can't really see that this is a 5.12 showstopper. It's present in 5.8.x, and is just one of a whole class of bugs wherein -- |
From @obraBased on comments from Tim Bunce, I'm removing this as a 5.12 blocker. |
1 similar comment
From @obraBased on comments from Tim Bunce, I'm removing this as a 5.12 blocker. |
From @timbunceOn Mon, Jan 11, 2010 at 11:04:03PM +0000, Dave Mitchell wrote:
I'd just like to wave the flag for this bug again. Tim. |
From @jkeenanOn Mon Jan 11 15:04:29 2010, davem wrote:
Was this overhaul of the line number operating system ever undertaken? Thank you very much. |
From @cpansproutOn Fri Apr 20 18:03:49 2012, jkeenan wrote:
I don’t think so. -- Father Chrysostomos |
From @rjbs* James E Keenan via RT <perlbug-followup@perl.org> [2012-04-20T21:03:49]
No. -- |
Migrated from rt.perl.org#60954 (status was 'open')
Searchable as RT60954$
The text was updated successfully, but these errors were encountered: