From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28665 invoked by alias); 19 Sep 2013 06:51:20 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 28644 invoked by uid 48); 19 Sep 2013 06:51:20 -0000 From: "forum at emblocks dot org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/15970] New: GDB is hanging in a recursive loop at dwarf_decode_macro_bytes in dwarf2read Date: Thu, 19 Sep 2013 06:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: 7.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: forum at emblocks dot org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-q3/txt/msg00378.txt.bz2 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.