-
Notifications
You must be signed in to change notification settings - Fork 569
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
segfault in perl_clone(), probably due to running out of memory #9332
Comments
From @ntyniThis is a bug report for perl from Niko Tyni <ntyni@debian.org>, As reported in <http://bugs.debian.org/343690>, the attached script Note that unlimiting the process stack size ('ulimit -s unlimited' or the Severity set to "low" because I assume the system is running out of Backtrace on 5.10.0 follows. The resulting core file is obscenely big. The % debugperl ~/t.pl sid% debugperl ~/t.pl #0 0x00000000004833bf in S_more_bodies (my_perl=0x1d50da0, sv_type=SVt_PVAV) at sv.c:1065 Flags: Site configuration information for perl 5.10.0: Configured by Debian Project at Thu May 8 11:57:24 UTC 2008. Summary of my perl5 (revision 5 version 10 subversion 0) configuration: Locally applied patches: @INC for perl 5.10.0: Environment for perl 5.10.0: |
From @jimcfg with -Dm also, it segfaults quickly dmesg says: the abababb3 looks a lot like a poisoned addr: = abababab + 8 I get lots of segvs in the spawned threads Thread creation failed: pthread_create returned 11 at |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#54224 (status was 'open')
Searchable as RT54224$
The text was updated successfully, but these errors were encountered: