This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [Patch] Use "<unknown>" instead of NULL when a symbol isn't found
- From: Tom Tromey <tromey at redhat dot com>
- To: Sterling Augustine <saugustine at google dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>, Keith Seitz <keiths at redhat dot com>
- Date: Fri, 20 Dec 2013 11:16:36 -0700
- Subject: Re: [Patch] Use "<unknown>" instead of NULL when a symbol isn't found
- Authentication-results: sourceware.org; auth=none
- References: <CAEG7qUxE2eiqv0nGe6=UJ9NpsgCAf0WtG2VPtiJpczaWatxwmg at mail dot gmail dot com>
>>>>> "Sterling" == Sterling Augustine <saugustine@google.com> writes:
Sterling> Although the case is hard to tickle--I only found it myself with an
Sterling> object file with an erroneous line table entry--GDB shouldn't crash,
Sterling> and recovery is quite straight-forward.
I wonder whether some correction or workaround is required elsewhere.
Sterling> The following patch simply assigns the symbol name as "<unknown>"
Sterling> instead of NULL, allowing the debugger to make forward progress in the
Sterling> face of an erroneous debug line table entry.
You didn't say whether you regression-tested this; but assuming so, it
is ok.
Tom