From: "Robert Norton" <rnorton@broadcom.com>
To: gdb@sourceware.org
Subject: Debugging with multiple sections in assembly files.
Date: Fri, 16 Nov 2007 13:22:00 -0000 [thread overview]
Message-ID: <B0D822BFECD50F4991F2516EA50F273C034F6988@NT-IRVA-0752.brcm.ad.broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Hi,
The attached tar contains source and a Makefile for two test programs.
One program includes an assembly file with two functions in the default
.text section, and the other contains a file with one function in .text
and another in a section 'foo'. With the first program gdb is able to
find the source for the assembly functions, for the other it is not:
(gdb) info line bar
Line 3 of "test_nosections.S" starts at address 0x400490 <bar> and ends
at 0x400491 <bling>.
---
(gdb) info line bar
No line number information available for address 0x400490 <bar>
The problem appears to be that in the case of the multi section asm file
gcc doesn't emit DW_AT_low_pc and DW_AT_high_pc for the assembly file
compile unit (try 'make dwarf.diff') because they don't make much sense
in that case. This means that gdb doesn't load the dwarf symbols for
that file and hence can't find source line information (as shown by
running 'info sources' before and after 'info line bar' -- try 'make
all').
Is this a known issue? Can it be fixed easily?
I tested with fairly recent gdb and gcc, but not latest HEAD versions.
Thanks,
Robert
[-- Attachment #2: asm_gdb.tar.gz --]
[-- Type: application/x-gzip, Size: 618 bytes --]
next reply other threads:[~2007-11-16 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 13:22 Robert Norton [this message]
2007-11-16 15:33 ` Daniel Jacobowitz
2007-11-17 12:17 ` Jan Kratochvil
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=B0D822BFECD50F4991F2516EA50F273C034F6988@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