-
Notifications
You must be signed in to change notification settings - Fork 559
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
Silent self-termination of script using regex. #8330
Comments
From [email protected]The following script self terminates silently. No segfault or warning or Panic. On someone elses Win32 system it aborts at around 31300. #! perl -w my $str = 'a' x 100000; for my $n ( map{ $_ * 1000 + 165 } 1 .. 30 ) { __END__ Perl Info
|
From @nwc10On Wed, Feb 08, 2006 at 03:15:30PM -0800, nigelsandever @ btconnect. com wrote:
Curiously blead on FreeBSD under valgrind it terminates without any perl The stack trace under gdb looks like this: #245 0x08171e24 in S_regmatch (my_perl=0x81f0000, prog=0x81ee258) etc Line 3520 is the call to regmatch in: if (n < cc->min) { Line 4026 is the call to regmatch in the TRYPAREN in: /* PL_reginput == old now */ I don't know why it's blowing the stack like this. Nicholas Clark |
The RT System itself - Status changed from 'new' to 'open' |
From [email protected]2006-02-18 16:48:59, "Nicholas Clark via RT" <perlbug-followup@perl.org> wrote:
Nichlolas, Whether this is useful or not I'm not sure, but if I run the snippet under a Perl.exe has encountered an exception code of -1073741571 (0xC00000FD)at and it shows a stack overflow: PID: 1932 (0x78C) TID: 1552 (0x610) Exception: STACK_OVERFLOW Address: 2805B3A1 and the stack trace lists 42340 calls to Perl_regexec_flags(), which is pretty PID: 656 TID: 1812 - Stack Contents for 0x2805B3A1 The last two of whihc repeat 43300 times until 0x2805DA71: perl58.dll:Perl_regexec_flags + 0x33BD Which looks to me like runaway recursion, but the source doesn't show any direct If I can help in any way, tell me what I can do? Cheers, njs |
From @nwc10On Mon, Feb 20, 2006 at 09:56:46PM -0000, Nigel Sandever wrote:
I'm afraid I can't help with any suggestions here. Having identified it as Nicholas Clark |
From @smpeters
It sounds like you were getting some sort of silent GPF or something steve@kirk:~/smoke/perl-current$ perl rt_38470.pl |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#38470 (status was 'resolved')
Searchable as RT38470$
The text was updated successfully, but these errors were encountered: