bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/24181] Memory leak in objdump


From: zhangyn2012 at bupt dot edu.cn
Subject: [Bug binutils/24181] Memory leak in objdump
Date: Wed, 06 Feb 2019 08:14:07 +0000

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

zhangyn2012 at bupt dot edu.cn changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.26                        |2.32

--- Comment #2 from zhangyn2012 at bupt dot edu.cn ---

A memory leak is triggered in objdump with `objdump -SD poc`:


==26079==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 200 byte(s) in 1 object(s) allocated from:
    #0 0x7fafefbb9602 in malloc
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
    #1 0x492383 in bfd_malloc
/home/zyn/Lollycode/tested/binutils/poc/binutils-2.32/bfd/libbfd.c:275
    #2 0x56cec7 in save_section_vma dwarf2.c:4269
    #3 0x56cec7 in _bfd_dwarf2_slurp_debug_info dwarf2.c:4354
    #4 0x56e085 in _bfd_dwarf2_find_nearest_line dwarf2.c:4562
    #5 0x50501c in _bfd_elf_find_nearest_line
/home/zyn/Lollycode/tested/binutils/poc/binutils-2.32/bfd/elf.c:8869
    #6 0x41099b in show_line objdump.c:1586
    #7 0x41099b in disassemble_bytes objdump.c:1901
    #8 0x414099 in disassemble_section objdump.c:2510
    #9 0x4992d3 in bfd_map_over_sections
/home/zyn/Lollycode/tested/binutils/poc/binutils-2.32/bfd/section.c:1374
    #10 0x409e6c in disassemble_data objdump.c:2647
    #11 0x40e4ac in dump_bfd objdump.c:3824
    #12 0x40f8c7 in display_object_bfd objdump.c:3883
    #13 0x40f8c7 in display_any_bfd objdump.c:3973
    #14 0x414cac in display_file objdump.c:3994
    #15 0x405e1a in main objdump.c:4304
    #16 0x7fafef57382f in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x2082f)

SUMMARY: AddressSanitizer: 200 byte(s) leaked in 1 allocation(s).

-- 
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]