-
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
any perl versions core dumps with this code #5739
Comments
From sem@ciam.ruCreated by sem@ciam.ruThis code always make perl core dump: Perl 5.005, 5.6.x and 5.8.0 was tested. Perl Info
|
From @nwc10On Wed, Jul 17, 2002 at 06:09:11PM -0000, sem@ciam.ru (via RT) wrote:
I can't get your code to crash on FreeBSD 4.6 with perl (patchlevel 17521, sub stat_level_warning Program received signal SIGSEGV, Segmentation fault. PL_curpad[po] was 0x19 on your version of the code. Running under valgrind I see this: nick@penfold:~/build$ valgrind /usr/local/perl17559-g/bin/perl5.8.0 crash (that same perl and same script will SEGV when not running under valgrind) I don't know what to do next, but I hope that this information is useful to Nicholas Clark |
From perlbug@perl.orgOn Wed, Jul 17, 2002 at 06:09:11PM -0000, sem@ciam.ru (via RT) wrote:
I can't get your code to crash on FreeBSD 4.6 with perl (patchlevel 17521, sub stat_level_warning Program received signal SIGSEGV, Segmentation fault. PL_curpad[po] was 0x19 on your version of the code. Running under valgrind I see this: nick@penfold:~/build$ valgrind /usr/local/perl17559-g/bin/perl5.8.0 crash (that same perl and same script will SEGV when not running under valgrind) I don't know what to do next, but I hope that this information is useful to Nicholas Clark |
From @floatingatoll[nick@unfortu.net - Wed Jul 17 12:55:36 2002]:
Reduced the test case to: #!perl Running perl with -Dl gives you some interesting output:
Included also are a gdb and valgrind against @17821, redhat x86, ithreads. R. ===> gdb stack trace, perl@17821 Program received signal SIGSEGV, Segmentation fault. ===> valgrind 1.0.1 output ==32201== valgrind-1.0.1, a memory error detector for x86 GNU/Linux. ===> ./perl -Dl 15005.pl |
From spamme@gameknot.comHere's another example of the code that causes the compiler to seg fault #!/usr/bin/perl |
From @jhiPerl has now been patched to give the following error: |
@jhi - Status changed from 'new' to 'resolved' |
Migrated from rt.perl.org#15005 (status was 'resolved')
Searchable as RT15005$
The text was updated successfully, but these errors were encountered: