From: "Robert Norton" <rnorton@broadcom.com>
To: gdb@sourceware.org
Subject: Bug handling zero sized symbols in minsyms.c
Date: Wed, 02 Jul 2008 17:00:00 -0000 [thread overview]
Message-ID: <B0D822BFECD50F4991F2516EA50F273C07A0A2CF@NT-IRVA-0752.brcm.ad.broadcom.com> (raw)
Hi,
In minsyms.c:lookup_minimal_symbol_by_pc_section() there is some code
which attempts to prefer symbols with sizes over those with zero size.
This is quite useful[1]. Unfortunately the present code will only work
if there is at most one zero-sized symbol. The fix is around line 503:
if (MSYMBOL_SIZE (&msymbol[hi]) == 0
&& best_zero_sized == -1)
{
best_zero_sized = hi;
hi--;
continue;
}
SHOULD be:
if (MSYMBOL_SIZE (&msymbol[hi]) == 0)
{
if (best_zero_sized == -1)
best_zero_sized = hi;
hi--;
continue;
}
We keep the highest zero-sized symbol as the best but continue to
iterate backwards until we hit a non-zero-sized symbol or run out of
symbols. It's pretty clear that this is what was originally intended.
I can get copyright assigment for this if required although it seems
pretty trivial...
Cheers,
Robert
[1] In particular it is useful when debugging assembly functions which
have internal labels for loops etc. Without this fix we sometimes get
back a minsym corresponding to an internal label (e.g. a loop) when
really what we wanted was the function symbol. This messes up prologue
analysis and some other things. For example in our GDB port the assembly
file:
.global main
main:
nop
test2:
nop
test3:
nop
.size main,.-main
.type main,@function
results in:
(gdb) info sym test2
main + 8 in section .text
(gdb) info sym test3
test3 in section .text <----------------- !!!
(gdb) disas main
Dump of assembler code for function main:
0x00000270 <main+0>: NOP
0x00000278 <main+8>: NOP
0x00000280 <test3+0>: NOP <----------------- !!!
End of assembler dump.
and in a patched version:
(gdb) info sym test2
main + 8 in section .text
(gdb) info sym test3
main + 16 in section .text
(gdb) disas main
Dump of assembler code for function main:
0x00000270 <main+0>: NOP
0x00000278 <main+8>: NOP
0x00000280 <main+16>: NOP
End of assembler dump.
RCS file: /cvs/dev/tools/src/binutils/gdb/minsyms.c,v
retrieving revision 1.3
diff -u -r1.3 minsyms.c
--- minsyms.c 4 Jan 2008 18:33:25 -0000 1.3
+++ minsyms.c 2 Jul 2008 16:36:02 -0000
@@ -503,10 +503,10 @@
symbol isn't an object or function (e.g. a
label), or it may just mean that the size was not
specified. */
- if (MSYMBOL_SIZE (&msymbol[hi]) == 0
- && best_zero_sized == -1)
+ if (MSYMBOL_SIZE (&msymbol[hi]) == 0)
{
- best_zero_sized = hi;
+ if (best_zero_sized == -1)
+ best_zero_sized = hi;
hi--;
continue;
}
next reply other threads:[~2008-07-02 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 17:00 Robert Norton [this message]
2008-07-02 17:45 ` Michael Snyder
2008-07-03 10:17 ` Robert Norton
2008-08-06 11:18 ` Robert Norton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B0D822BFECD50F4991F2516EA50F273C07A0A2CF@NT-IRVA-0752.brcm.ad.broadcom.com \
--to=rnorton@broadcom.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox