-
Notifications
You must be signed in to change notification settings - Fork 571
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 5.20.2 - SIGSEV #14819
Comments
From espinhara.net@gmail.comHi all. I'm doing a fuzzing in a specific library, but I found this crash that for The crash was found using the afl-fuzzer (http://lcamtuf.coredump.cx/afl) root@linux-base:~/perl-5.20.2# perl -v This is perl 5, version 20, subversion 2 (v5.20.2) built for x86_64-linux Copyright 1987-2015, Larry Wall Perl may be copied only under the terms of either the Artistic License or Complete documentation for Perl, including FAQ lists, should be found on root@linux-base:~/perl-5.20.2# root@linux-base:~/out_perl/crashes# valgrind perl id\:000001\,sig\:11\,src\: gdb-peda$ r < id:000001,sig:11,src:000696,op:havoc,rep:32 Program received signal SIGSEGV, Segmentation fault. Also the same file is able to cause a crash in OSx Perl => *This is perl 5, Process: perl5.18 [9650] Date/Time: 2015-07-27 19:36:25.843 +1000 Sleep/Wake UUID: 577DBAD8-FA8D-49DD-A2A6-46A3D909EC56 Time Awake Since Boot: 51000 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) VM Regions Near 0x7fc659600000: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 6 Binary Images: External Modification Summary: VM Region Summary: REGION TYPE VIRTUAL -- |
From @tonycozOn Mon Jul 27 02:38:49 2015, espinhara.net@gmail.com wrote:
It looks like this was fixed in 4963771 (v5.21.0-429-g4963771), but that patch doesn't appear to be directly applicable to maint-5.20 since it depends on the ?...? operator being removed. Tony |
The RT System itself - Status changed from 'new' to 'open' |
From @tonycozOn Tue Sep 15 18:25:36 2015, tonyc wrote:
Here's a simpler crash case (attached) tony@mars:.../git/perl$ ./perl ../125697b.pl which feels familiar. Tony |
From @tonycoz |
From @tonycozOn Tue, 15 Sep 2015 18:25:36 -0700, tonyc wrote:
This is fixed in both supported releases, so closing. Tony |
@tonycoz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125697 (status was 'resolved')
Searchable as RT125697$
The text was updated successfully, but these errors were encountered: