-
Notifications
You must be signed in to change notification settings - Fork 555
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
Perl Segmentation Fault using /((\w+ )+)/ on long strings #5141
Comments
From suter@zwitterion.humbug.org.auCreated by suter@zwitterion.humbug.org.auOne all the systems I tested the following on, it exits with a perl -e '("bug " x 1E5) =~ /((\w+ )+)/' Perl Info
|
From @nwc10On Tue, Feb 26, 2002 at 03:15:14PM +1000, Mark Suter wrote:
This appears to be a bug introduced between 5.005_03 and 5.6.0 $ perl5.00404 -e '("bug " x 1E5) =~ /((\w+ )+)/' [on ARM linux, still present at patch 14826] I've just built 14951 on x86 FreeBSD with -g and I can't get that to SEGV. In 13520 on ARM with -g it's here: Program received signal SIGSEGV, Segmentation fault. In perl with "DEVEL11709" in patchlevel.h it's here: Program received signal SIGSEGV, Segmentation fault. (gdb) list (gdb) print next Odd. 0x12fe90 <S_regmatch+18876>: This is the SEGV instruction, the the assignment to s. 0x12feb0 <S_regmatch+18908>: str r2, [r11, -#224] These are the registers r0 0x1751e4 1528292 $ perl -le 'printf "%x\n", 0xbf800074-224' So we're string to store the contents of R2 at bf7fff94, which is above perl5.7.2-g: unhandled page fault at pc=0x0012feb0, lr=0x0012efec (bad address=0xbf7fff94, code -1) And I have no idea what a code -1 is. So I'm going to check with the ARM Linux But it's a real bug. Thanks for the report. Nicholas Clark |
From @schwernOn Sun, Mar 03, 2002 at 12:17:01AM +0000, Nicholas Clark wrote:
I can. Debian/PowerPC. $ perl5.6.0 -e '("bug " x 1E5) =~ /((\w+ )+)/' that's @14897. Same problem, big stack of S_regmatch calls. -- Michael G. Schwern <schwern@pobox.com> http://www.pobox.com/~schwern/ |
From @andk
> that's @14897. Same problem, big stack of S_regmatch calls. Is it not the standard out-of-stack problem? I have the impression, http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/1999-03/msg00645.html It's only a matter of the length of the string. If a specific perl -- |
From @jhiOn Sun, Mar 03, 2002 at 12:52:07PM +0100, Andreas J. Koenig wrote:
I think it is. It cores on me in Tru64, but simply by growing the
-- |
From @smpeters
This appears to have been fixed with change #27598. steve@kirk:~/smoke/perl-current$ perl -e '("bug " x 1E5) =~ /((\w+ )+)/' |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#8685 (status was 'resolved')
Searchable as RT8685$
The text was updated successfully, but these errors were encountered: