public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/12703] Different function breakpoints are set at same pc address.
Date: Fri, 06 May 2011 04:17:00 -0000 [thread overview]
Message-ID: <bug-12703-4717-9bUvZkdImF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12703-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12703
Yao Qi <qiyao at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qiyao at gcc dot gnu.org
--- Comment #3 from Yao Qi <qiyao at gcc dot gnu.org> 2011-05-06 04:17:03 UTC ---
>
> I looked into the function arm_skip_prologue which uses limit_pc to indicate
> the range of prologue. If it fails to get an acute pc boundary, it will use
> pc+64 as limit_pc. For my case, the pc+64 exceeds the body of function
> fault_isr and reaches the prologue of following function reset_isr. This
> mechanism cause GDB to set two different function points at the same pc
> address.
This fix works, however, IMO, the root cause is that thumb_analyze_prologue is
unable to compute/analyze such prologue in your case.
>
> I come up with attached patch to ensure the limit_pc shouldn't exceed the body
> of current functions. It fixes this issue.
Please send your patch to gcc-patches@, then maintainers can review/approve it.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-05-06 4:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 3:22 [Bug breakpoints/12703] New: " terry.guo at arm dot com
2011-04-26 3:33 ` [Bug breakpoints/12703] " terry.guo at arm dot com
2011-04-26 3:34 ` terry.guo at arm dot com
2011-05-06 4:17 ` qiyao at gcc dot gnu.org [this message]
2011-10-13 8:17 ` cvs-commit at gcc dot gnu.org
2011-10-13 8:24 ` qiyao at gcc dot gnu.org
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=bug-12703-4717-9bUvZkdImF@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).