public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/14014] New: win64 crash with bad dwarf2 symbols (7.4 crash / 7.3 gives error expected)
@ 2012-04-24 13:35 gdb.bugs at mfriebe dot de
  2012-04-24 20:20 ` [Bug gdb/14014] " tromey at redhat dot com
  0 siblings, 1 reply; 2+ messages in thread
From: gdb.bugs at mfriebe dot de @ 2012-04-24 13:35 UTC (permalink / raw)
  To: gdb-prs

http://sourceware.org/bugzilla/show_bug.cgi?id=14014

             Bug #: 14014
           Summary: win64 crash with bad dwarf2 symbols (7.4 crash / 7.3
                    gives error expected)
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: gdb.bugs@mfriebe.de
    Classification: Unclassified


Created attachment 6361
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6361
source and exe

Windows 64 bit XP Sp2 (though probably affects any 64 bit win) Intel

Free pascal version 2.4.4 does generate broken dwarf2 info. It is expected that
gdb reports errors in an attempt to use them.

GDB 7.3 reports such errors as expected
GDB 7.4 crashes

Attached is a simple pascal program, and the exe compiled with fpc 2.4.4 (must
be 2.4.4 / other fpc do not generate the required broken dwarf)

The source was compiled using:
   fpc.exe  -gw  hello.pas

GDB was downloaded from http://www.drangon.org/mingw/  
mingw-w64-bin-x86_64-20120225.7z : native mingw-w64 toolchain under Windows
XP/2003 x64, build (gcc 4.6 branch) from SVN 2012-02-25 (29M)
 
http://www.drangon.org/mingw/mirror.php?num=2&fname=mingw-w64-bin-x86_64-20120225.7z

Run gdb as follows:
  gdb.exe -i mi hello.exe
Then enter
   -break-insert main
this crashes gdb 7.4


While this is primarily an issue of fpc and while such a broken file can not be
debugged, it still should not lead to a crash. Especially since previous gdb
versions were able to detect the error

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug gdb/14014] win64 crash with bad dwarf2 symbols (7.4 crash / 7.3 gives error expected)
  2012-04-24 13:35 [Bug gdb/14014] New: win64 crash with bad dwarf2 symbols (7.4 crash / 7.3 gives error expected) gdb.bugs at mfriebe dot de
@ 2012-04-24 20:20 ` tromey at redhat dot com
  0 siblings, 0 replies; 2+ messages in thread
From: tromey at redhat dot com @ 2012-04-24 20:20 UTC (permalink / raw)
  To: gdb-prs

http://sourceware.org/bugzilla/show_bug.cgi?id=14014

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-04-24 20:18:54 UTC ---
With CVS gdb I get:

(gdb) b main
invalid dwarf2 offset 118916

... which is really quite unfriendly, but at least it doesn't crash.

I'm not going to close the bug, since I think we ought to fix
the error message to convey enough information to diagnose the
problem.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-04-24 20:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-24 13:35 [Bug gdb/14014] New: win64 crash with bad dwarf2 symbols (7.4 crash / 7.3 gives error expected) gdb.bugs at mfriebe dot de
2012-04-24 20:20 ` [Bug gdb/14014] " tromey at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).