From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: Re: Debugging with multiple sections in assembly files.
Date: Fri, 16 Nov 2007 15:33:00 -0000 [thread overview]
Message-ID: <20071116153338.GA8036@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C034F6988@NT-IRVA-0752.brcm.ad.broadcom.com>
On Fri, Nov 16, 2007 at 05:14:54AM -0800, Robert Norton wrote:
> 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').
s/gcc/gas/. gas needs to generate DW_AT_ranges, I would imagine.
This looks to me like:
2006-08-08 Sterling Augustine <sterling@tensilica.com>
* dwarf2dbg.c (out_debug_info): Add new parameter ranges_seg
and emit DW_AT_ranges when code in compilation unit is not
contiguous.
(out_debug_abbrev): Emit DW_AT_ranges abbreviation if code in
is not contiguous.
(dwarf2_finish): Create and pass ranges_seg to out_debug_info.
(out_debug_ranges): New function to emit .debug_ranges section
when code is not contiguous.
Is that patch in your assembler? If not, can you try a newer one?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-11-16 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 13:22 Robert Norton
2007-11-16 15:33 ` Daniel Jacobowitz [this message]
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=20071116153338.GA8036@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rnorton@broadcom.com \
/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