public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "martin at minimum dot se" <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 13:41:00 -0000	[thread overview]
Message-ID: <bug-17384-4717-zaVLXu83rz@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 #4 from molsson <martin at minimum dot se> ---
You're right, there was infact 5 calls to memory_error() during the relevant
"stepi" and it was only after I "continue" past the 5th one that the error is
printed. The bt to that last memory_error() call is:

#0  read_memory (memaddr=1, myaddr=0x7ffff71ed760 <incomplete sequence \360>,
len=4) at corefile.c:247
#1  0x000000000060a81e in read_memory_integer (memaddr=1, len=4,
byte_order=BFD_ENDIAN_LITTLE) at corefile.c:357
#2  0x000000000060a774 in do_captured_read_memory_integer (data=0x7ffff71ed850)
at corefile.c:322
#3  0x0000000000564fae in catch_errors (func=0x60a72d
<do_captured_read_memory_integer>, func_args=0x7ffff71ed850, errstring=0x848451
"", mask=RETURN_MASK_ALL) at exceptions.c:237
#4  0x000000000060a7cb in safe_read_memory_integer (memaddr=1, len=4,
byte_order=BFD_ENDIAN_LITTLE, return_value=0x7ffff71ed8d0) at corefile.c:343
#5  0x000000000040e07c in arm_scan_prologue (this_frame=0x301f6c90,
cache=0x301f6d50) at arm-tdep.c:1996
#6  0x000000000040e141 in arm_make_prologue_cache (this_frame=0x301f6c90) at
arm-tdep.c:2022
#7  0x000000000040e230 in arm_prologue_this_id (this_frame=0x301f6c90,
this_cache=0x301f6ca8, this_id=0x301f6cf0) at arm-tdep.c:2052
#8  0x00000000006870ce in compute_frame_id (fi=0x301f6c90) at frame.c:459
#9  0x0000000000689b2e in get_prev_frame_if_no_cycle (this_frame=0x301f6300) at
frame.c:1781
#10 0x000000000068a1c5 in get_prev_frame_always_1 (this_frame=0x301f6300) at
frame.c:1955
#11 0x000000000068a215 in get_prev_frame_always (this_frame=0x301f6300) at
frame.c:1972
#12 0x000000000068728f in frame_unwind_caller_id (next_frame=0x301f6300) at
frame.c:500
#13 0x0000000000553be1 in process_event_stop_test (ecs=0x7ffff71ee0e0) at
infrun.c:4738
#14 0x0000000000553016 in handle_signal_stop (ecs=0x7ffff71ee0e0) at
infrun.c:4304
#15 0x0000000000552041 in handle_inferior_event (ecs=0x7ffff71ee0e0) at
infrun.c:3797
#16 0x000000000055051d in fetch_inferior_event (client_data=0x0) at
infrun.c:2899
#17 0x0000000000572a6e in inferior_event_handler (event_type=INF_REG_EVENT,
client_data=0x0) at inf-loop.c:58
#18 0x000000000044e435 in remote_async_serial_handler (scb=0x1d2c610,
context=0x1c46b90) at remote.c:11586
#19 0x0000000000436aba in run_async_handler_and_reschedule (scb=0x1d2c610) at
ser-base.c:137
#20 0x0000000000436b8a in fd_event (error=0, context=0x1d2c610) at
ser-base.c:182
#21 0x000000000057086f in handle_file_event (data=...) at event-loop.c:763
#22 0x000000000056fd44 in process_event () at event-loop.c:340
#23 0x000000000056fe0b in gdb_do_one_event () at event-loop.c:404
#24 0x000000000056fe5b in start_event_loop () at event-loop.c:429
#25 0x00000000005718d6 in cli_command_loop (data=0x0) at event-top.c:182
#26 0x00000000005681cd in current_interp_command_loop () at interps.c:318
#27 0x0000000000568d79 in captured_command_loop (data=0x0) at main.c:322
#28 0x0000000000564fae in catch_errors (func=0x568d5e <captured_command_loop>,
func_args=0x0, errstring=0x81a8f5 "", mask=RETURN_MASK_ALL) at exceptions.c:237
#29 0x000000000056a21e in captured_main (data=0x7ffff71ee560) at main.c:1142
#30 0x0000000000564fae in catch_errors (func=0x569153 <captured_main>,
func_args=0x7ffff71ee560, errstring=0x81a8f5 "", mask=RETURN_MASK_ALL) at
exceptions.c:237
#31 0x000000000056a247 in gdb_main (args=0x7ffff71ee560) at main.c:1150
#32 0x00000000004062cd in main (argc=3, argv=0x7ffff71ee668) at gdb.c:32

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-09-16 13:41 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
2014-09-16 13:41 ` martin at minimum dot se [this message]
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-zaVLXu83rz@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).