This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/14261] Break point not set at the 1st executable instruction in case of code compiled with clang on ARM Architecture.
- From: "will.newton at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 30 Oct 2013 23:18:23 +0000
- Subject: [Bug gdb/14261] Break point not set at the 1st executable instruction in case of code compiled with clang on ARM Architecture.
- Auto-submitted: auto-generated
- References: <bug-14261-4717 at http dot sourceware dot 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.