From: wangjiong@sunnorth.com.cn
To: gdb@sourceware.org
Subject: Re: Question about Dwarf2 for VLIW processor
Date: Thu, 08 Nov 2007 01:27:00 -0000 [thread overview]
Message-ID: <OFD216B7C7.FF53B16F-ON4825738D.0007D79C-4825738D.0007E87C@sunnorth.com.cn> (raw)
Dear Joel:
I am using GDB6.1.1
GDB did not stop at the wrong location now, but I have see that
the function:
find_pc_line_pc_range (stop_pc, &step_range_start,
&step_range_end) didn`t work correctly.
when stop_pc is 0x8000035 the returned value of step_range_start
and step_range_end is
0x800003c5 and 0x800003cb
but they should be
0x800003c5 and 0x800003cf
I have found all these are because there is something wrong with
the Dwarf2 .debug_line section.
Now every instruction has a entry in this section, maybe it should
be every c statement.
Cause I can not modify compiler or assembler now, So I want to
know How can I solve this problem
just within GDB.
Thanks.
Wang Jiong
tel:2254
next reply other threads:[~2007-11-08 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 1:27 wangjiong [this message]
2007-11-08 1:41 ` Daniel Jacobowitz
2007-11-08 1:54 ` wangjiong
2007-11-08 2:12 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2007-11-07 6:17 wangjiong
2007-11-07 19:17 ` Joel Brobecker
2007-11-08 1:25 ` wangjiong
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=OFD216B7C7.FF53B16F-ON4825738D.0007D79C-4825738D.0007E87C@sunnorth.com.cn \
--to=wangjiong@sunnorth.com.cn \
--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