-
Notifications
You must be signed in to change notification settings - Fork 550
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
Wrong context determined for <>/IO::Handle::getline in debug mode #15698
Comments
From @KES777Created by @KES777Sorry, can not replay to https://rt.perl.org/Public/Bug/Display.html?id=92728 When I debug my script and it is use IO::Handle I got errors issued from: $ mojo generate lite_ap I modify IO::Handle to look like: sub getlines { DB::getline(); # line 460 And I get this error: DDD>>>DB at lib/Devel/DebugHooks.pm line 1439. I suppose context in debugger mode is not determined right by _create_getline_subs Perl Info
|
From @jkeenanOn Fri, 04 Nov 2016 22:58:10 GMT, kes-kes@yandex.ru wrote:
This report does not appear to be appropriate for rt.perl.org.
That RT was closed more than five years ago. It's not clear why you were trying to reply to it.
In my experience, this error message appears when I fail to say: ##### Could you try that first? Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Fri, 04 Nov 2016 16:18:11 -0700, jkeenan wrote:
The line in question is actually in IO::Handle, which already does ‘use Carp’. There appears to be some ugly interaction between a sub that has no nextstate ops and the debugger. I wonder whether it affects subs in the CORE:: namespace too, as they use a similar trick to run code with the caller’s hints. -- Father Chrysostomos |
From @KES777I minify testcase. This is occur only when I do call to Time::HiRes::gettimeofday $ cat Devel/DB.pm sub DB { use Time::HiRes qw/ gettimeofday /; return &$DB::sub; 1; $ cat t.pl $ perl -d:DB t.pl |
Migrated from rt.perl.org#130021 (status was 'open')
Searchable as RT130021$
The text was updated successfully, but these errors were encountered: