From: Daniel Jacobowitz <drow@false.org>
To: qinwei <qinwei@sunnorth.com.cn>
Cc: gdb@sourceware.org
Subject: Re: How to avoid "but contains no code." in command "info line"?
Date: Fri, 23 Mar 2007 11:58:00 -0000 [thread overview]
Message-ID: <20070323115751.GB27943@caradoc.them.org> (raw)
In-Reply-To: <OF59439A6E.C25A10FF-ON482572A7.00264C6A-482572A7.00286B8B@sunnorth.com.cn>
On Fri, Mar 23, 2007 at 03:21:29PM +0800, qinwei wrote:
> Dears, problems are here:
>
> In a assembly file 'a.s', we define two sections which have code both.
> For example:
>
> line1: .section mysection
> line2: load r4, [r3]
> line3: jump func
> ......
>
> line6: .text
> line7: store r4, [r3]
> line8: jump func
> ......
>
> "info line a.s:7" will print both the begin and end address of the line.
> but "info line a.s:2" just print the begin address and "but contains no
> code."
>
> I trace the behavior of gdb (6.6 release) and find if the code is not in
> .text,
> then it will not be put to the 'blockvector structure'
Are you sure? It sounds to me like your assembler is not emitting the
right debug info. GDB doesn't care what section lines are in.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-23 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 7:22 qinwei
2007-03-23 11:58 ` Daniel Jacobowitz [this message]
2007-03-27 4:08 ` qinwei
2007-03-27 11:16 ` Daniel Jacobowitz
2007-03-28 2:46 ` qinwei
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=20070323115751.GB27943@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=qinwei@sunnorth.com.cn \
/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