-
Notifications
You must be signed in to change notification settings - Fork 584
Non assignment to *DB::DB causes segfault #12432
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
Comments
From @LeontThis is a bug report for perl from fawaka@gmail.com,
It seems pp_dbstate doesn't check it the &DB::DB is really defined, Flags: Site configuration information for perl 5.16.1: Configured by leon at Thu Aug 9 12:30:13 EEST 2012. Summary of my perl5 (revision 5 version 16 subversion 1) configuration: Platform: Locally applied patches: @INC for perl 5.16.1: Environment for perl 5.16.1: |
From [Unknown Contact. See original ticket]Fixed in 432d456. |
@doy - Status changed from 'new' to 'resolved' |
From [email protected]On Fri Sep 21 05:35:18 2012, LeonT wrote:
This seems familiar. Yup: bug #34892 -- a bug from years ago which If you know what caused this bug, maybe check all the other debugger Ambrus |
From [email protected]On Mon Sep 24 05:34:57 2012, b_jonas wrote:
In fact, you might be able to get a smaller test case for this bug using perl -we 'sub DB::DB; BEGIN { $^P = 0x22; } for (0 .. 9) { warn "hello This should give some kind of error or just print hello world ten times, Ambrus |
From @nwc10On Mon, Sep 24, 2012 at 05:40:02AM -0700, Zsban Ambrus via RT wrote:
Thanks for the terse test case.
I do, but I don't have time to investigate this further (until at least commit 432d456 don't crash with -d if DB::DB is seen but not defined [perl #114990] (gdb) r Program received signal SIGSEGV, Segmentation fault. Nicholas Clark |
From @cpansproutOn Mon Sep 24 05:40:01 2012, b_jonas wrote:
I’ve just fixed that in commit c2cb6f7. -- Father Chrysostomos |
Migrated from rt.perl.org#114990 (status was 'resolved')
Searchable as RT114990$
The text was updated successfully, but these errors were encountered: