public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "will.newton at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14261] Break point not set at the 1st executable instruction in case of code compiled with clang on ARM Architecture.
Date: Wed, 30 Oct 2013 23:18:00 -0000 [thread overview]
Message-ID: <bug-14261-4717-3zW7URBjB6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14261-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14261
Will Newton <will.newton at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |will.newton at gmail dot com
--- Comment #1 from Will Newton <will.newton at gmail dot com> ---
The prologue scanner appears to be checking for stores of varargs arguments in
the function prologue which is why this refers to r0-r3. It is not clear from
looking at the disassembly that you attached that these stores are actually
part of the prologue, they look like they are initializations of stack
variables.
Also your example with main does not correspond to the example in the zip.
Can you confirm that this problem is still valid?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-30 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 12:12 [Bug gdb/14261] New: " karthikthecool at gmail dot com
2013-10-30 23:18 ` will.newton at gmail dot com [this message]
2014-10-30 14:53 ` [Bug gdb/14261] " chrbr at gcc dot gnu.org
2014-10-30 14:56 ` chrbr at gcc dot gnu.org
2014-12-12 0:42 ` [Bug tdep/14261] " qiyao at gcc dot gnu.org
2014-12-12 0:52 ` cvs-commit at gcc dot gnu.org
2014-12-12 2:14 ` 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-14261-4717-3zW7URBjB6@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).