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/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"
Date: Tue, 16 Sep 2014 09:16:00 -0000 [thread overview]
Message-ID: <bug-17384-4717-NDD2niTnJY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17384-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17384
--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
I'm not exactly sure what's going on here, but the backtrace shows a memory
read coming from the prologue scanner, triggered probably from the code that
tries to determine whether the program stepped into a function:
#2 0x000000000058be11 in read_memory (memaddr=1,
...
#5 0x0000000000513225 in catch_errors (func=func@entry=0x58bef0
...
#6 0x000000000058be8b in safe_read_memory_integer (memaddr=<optimized out>,
#7 0x000000000041122a in arm_scan_prologue (cache=0x1e51ec0,
#8 arm_make_prologue_cache (this_frame=0x1e51e00) at arm-tdep.c:2022
...
#12 0x00000000005e72ca in get_prev_frame_always_1 (this_frame=0x1e51470) at
frame.c:1955
...
#15 0x0000000000503a07 in process_event_stop_test
(ecs=ecs@entry=0x7fff5dee9070) at infrun.c:4738
So it kind of sounds like either the program's stack really is corrupted, or,
GDB's heuristic prologue scanner gets this prologue wrong.
But the thing is that error you've shown is caught and swallowed (frames
#5/#6),
so it looks like this particular memory_error call can't result in the user
visible error. There's probably another one after if you let GDB continue.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-16 9:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 13:38 [Bug gdb/17384] New: " martin at minimum dot se
2014-09-16 8:48 ` [Bug gdb/17384] " martin at minimum dot se
2014-09-16 9:03 ` palves at redhat dot com
2014-09-16 9:16 ` palves at redhat dot com [this message]
2014-09-16 13:41 ` martin at minimum dot se
2014-09-16 13:46 ` martin at minimum dot se
2014-09-16 15:10 ` palves at redhat dot com
2014-09-17 7:57 ` martin at minimum dot se
2014-09-17 9:45 ` martin at minimum dot se
2014-09-17 10:20 ` palves at redhat dot com
2014-09-17 11:23 ` martin at minimum dot se
2014-09-17 11:38 ` palves at redhat dot com
2014-09-17 15:33 ` cvs-commit at gcc dot gnu.org
2014-09-18 7:15 ` martin at minimum dot se
2014-09-18 7:28 ` palves at redhat dot com
2014-09-18 7:33 ` palves at redhat dot com
2014-09-18 8:44 ` palves at redhat dot com
2014-09-18 17:40 ` palves at redhat dot com
2014-09-19 14:54 ` martin at minimum dot se
2014-09-19 15:25 ` palves at redhat dot com
2014-09-22 9:12 ` martin at minimum dot se
2014-09-22 13:12 ` qiyao at gcc dot gnu.org
2014-09-23 9:23 ` qiyao at gcc dot gnu.org
2014-09-23 12:50 ` martin at minimum dot se
2014-09-24 11:57 ` qiyao at gcc dot gnu.org
2014-10-09 8:10 ` qiyao at gcc dot gnu.org
2014-10-14 8:32 ` martin at minimum dot se
2014-10-14 11:01 ` martin at minimum dot se
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-17384-4717-NDD2niTnJY@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).