bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gprof/30532] New: SEGV in symtab_finalize


From: mengda2020 at iscas dot ac.cn
Subject: [Bug gprof/30532] New: SEGV in symtab_finalize
Date: Fri, 09 Jun 2023 10:18:34 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=30532

            Bug ID: 30532
           Summary: SEGV in symtab_finalize
           Product: binutils
           Version: 2.39
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gprof
          Assignee: unassigned at sourceware dot org
          Reporter: mengda2020 at iscas dot ac.cn
  Target Milestone: ---

Created attachment 14927
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14927&action=edit
input file

Hello, Binutils developers! We recently ran some fuzz testing on gprof 2.39 and
encountered a SEGV bug. 

## Command To Reproduce the bug:
./gprof $segv
segv is the attachment

## Environment
- OS: Ubuntu 20.04
- gcc 9.4.0
- gprof 2.39

## ASAN Report 
=================================================================
==958629==ERROR: AddressSanitizer: SEGV on unknown address 0x612ffffffef0 (pc
0x0000005086d9 bp 0x7ffe7d254980 sp 0x7ffe7d254580 T0)
==958629==The signal is caused by a READ memory access.
    #0 0x5086d9 in symtab_finalize
/home/root/sp/Dataset/Binutils/binutils_aflpp/gprof/symtab.c:150:40
    #1 0x50b9a8 in sym_id_parse
/home/root/sp/Dataset/Binutils/binutils_aflpp/gprof/sym_ids.c:363:7
    #2 0x4fcb34 in main
/home/root/sp/Dataset/Binutils/binutils_aflpp/gprof/gprof.c:539:3
    #3 0x7fe52cf3e082 in __libc_start_main
/build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
    #4 0x41d54d in _start
(/home/root/sp/Fuzz/aflpp_fuzz/Binutils/gprof/gprof_1/gprof+0x41d54d)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV
/home/root/sp/Dataset/Binutils/binutils_aflpp/gprof/symtab.c:150:40 in
symtab_finalize
==958629==ABORTING

Many Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]