public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16157] the function get_pc_function_start (CORE_ADDR pc) maybe inaccurate
Date: Wed, 13 Nov 2013 10:06:00 -0000 [thread overview]
Message-ID: <bug-16157-4717-mvITBqL1o6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16157-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16157
--- Comment #8 from Pedro Alves <palves at redhat dot com> ---
I feels like you're either ignoring half my suggestions, or not reading
carefully. It makes it hard for me to help you.
> > What's different between lop3 and lop2?
>No different from lop2 and lop3, only 2 labels.
I'm well aware they're too labels. But what makes it so that for instructions
between lop3 and lop2, gdb believes the function is _start, not lop3?
You still haven't checked for outer_frame_id.
> >BTW, if this is the case, this means that this issue only triggers when
> >stepping through code in the outermost frame (the entry point). IOW, iIf
> >your _start was actually some other function that was called by _start (so
> >that it'd wouldn't be the outermost frame), this issue wouldn't trigger.
> You are right! this issue only triggers when debugging assembler code!
Sure, except that's not what I said.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-13 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 6:12 [Bug gdb/16157] New: " guosheng_gao at realsil dot com.cn
2013-11-12 11:46 ` [Bug gdb/16157] " palves at redhat dot com
2013-11-12 13:01 ` guosheng_gao at realsil dot com.cn
2013-11-12 13:18 ` guosheng_gao at realsil dot com.cn
2013-11-12 14:29 ` palves at redhat dot com
2013-11-13 2:49 ` guosheng_gao at realsil dot com.cn
2013-11-13 3:10 ` guosheng_gao at realsil dot com.cn
2013-11-13 10:06 ` palves at redhat dot com [this message]
2013-11-14 9:57 ` guosheng_gao at realsil dot com.cn
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-16157-4717-mvITBqL1o6@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).