This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug corefiles/15970] New: GDB is hanging in a recursive loop at dwarf_decode_macro_bytes in dwarf2read


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

            Bug ID: 15970
           Summary: GDB is hanging in a recursive loop at
                    dwarf_decode_macro_bytes in dwarf2read
           Product: gdb
           Version: 7.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: corefiles
          Assignee: unassigned at sourceware dot org
          Reporter: forum at emblocks dot org

Created attachment 7209
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7209&action=edit
The used output file

An output file created by GCC (arm) with the debugging option -g3 (max info) is
causing a problem for GDB. This is now done with ARM but it's more a general
problem because it's in the target independent part of GDB. 

I have the output file included as attachment. 

Steps to reproduce:

GDB.exe  --interpreter=mi --args .\temp.elf

GDB> target remote localhost:xxxx (just make contact to a target so that the
symbols are reread)

GDB is hanging in a loopin the function dwarf_decode_macro_bytes in the file
dwarf2read and is consuming a lot of memory.

The output file is just a very small program but with a lot of macro
definitions for MCU access.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]