public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "christian.prochaska@genode-labs.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/13247] Wrong breakpoint address for ARM binary built with -O2
Date: Thu, 06 Oct 2011 15:29:00 -0000 [thread overview]
Message-ID: <bug-13247-4717-XKcQrlyhYs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13247-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13247
--- Comment #2 from Christian Prochaska <christian.prochaska@genode-labs.com> 2011-10-06 15:28:31 UTC ---
According to the comments linked from Bug 12573 the function prologue is not to
be skipped at all for -O2 and instead it is assumed that DWARF location
information is always correct. So I guess in my case the location information
is incorrect?
<2><175>: Abbrev Number: 6 (DW_TAG_formal_parameter)
<176> DW_AT_name : (indirect string, offset: 0x65): func1_args
<17a> DW_AT_decl_file : 1
<17b> DW_AT_decl_line : 3
<17c> DW_AT_type : <0x106>
<180> DW_AT_location : 2 byte block: 91 70 (DW_OP_fbreg: -16)
>From my current understanding, DW_AT_location is rather supposed to link to a
location list containing the information that a part of func1_args is stored in
registers for PC values 0x838c-0x8394 and in memory later, starting with PC
value 0x8398?
--
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.
prev parent reply other threads:[~2011-10-06 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 11:39 [Bug breakpoints/13247] New: " christian.prochaska@genode-labs.com
2011-10-05 16:09 ` [Bug breakpoints/13247] " christian.prochaska@genode-labs.com
2011-10-06 15:29 ` christian.prochaska@genode-labs.com [this message]
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-13247-4717-XKcQrlyhYs@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).