-
Notifications
You must be signed in to change notification settings - Fork 561
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
recently-introduced regex segfault #5279
Comments
From jfriedl@yahoo.comWith the latest bleedperl, this program segfaults if 're debug' is used. use overload; I'm fairly confident that this worked last week. (gdb) run -w -Ilib -Mre+debug /tmp/foo Program received signal SIGSEGV, Segmentation fault. Perl Info
|
From @schwernOn Sat, Mar 23, 2002 at 08:53:16PM -0800, Jeffrey Friedl wrote:
Only 'use overload' is necessary for me. It segfaults @15421 without -DDEBUGGING. Can't tell exactly where This appears to be the opposite of what you're seeing since line 1592
err.. what happened there? -- Michael G. Schwern <schwern@pobox.com> http://www.pobox.com/~schwern/ |
From @jhi
Repeated Configures without make distclean. (The hints files do -- |
From @schwernThe segfault *is* in the PERL_DEBUG_PAD_ZERO(0) call. Here's what (((XPV*) ( &(PL_debug_pad.pad[ 0 ]) )->sv_any )->xpv_pv [0] = 0, ((XPV*) ( &(PL_debug_pad.pad[ 0 ]) )->sv_any )->xpv_cur = 0, &(PL_debug_pad.pad[ 0 ]) ) ; pretty. PL_debug_pad does not seem to contain anything useful. (gdb) p PL_debug_pad and so those dereferences above will bomb. (gdb) p ((XPV*) ( &(PL_debug_pad.pad[ 0 ]) )->sv_any )->xpv_pv [0] This only happens if -DDEBUGGING is off. re.pm turns -DDEBUGGING back /* need access to debugger hooks */ I think what causes the problem is this code in perl.h: #ifdef DEBUGGING without -DDEBUGGING when perl.h is compiled DEBUGGING is off so the Solution? Remove the #ifdef DEBUGGING. --- perl.c 2002/03/24 07:20:56 1.1 -- Michael G. Schwern <schwern@pobox.com> http://www.pobox.com/~schwern/ |
From @jhi
Looks good to me. In fact I have a severe case of of dejavu... ahhh, yes: ____________________________________________________________________________ -- |
From @smpeters
____________________________________________________________________________
____________________________________________________________________________ This all appears to be working fine in multiple versions of 5.8 and |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#8870 (status was 'resolved')
Searchable as RT8870$
The text was updated successfully, but these errors were encountered: