[Bug gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"

["martin at minimum dot se" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17384

--- Comment #5 from molsson <martin at minimum dot se> ---
Sorry that last comment didn't make a lot of sense, I used the wrong
breakpoint.

If I put a breakpoint on memory_error_message() instead, which is the function
that prints the actual error. Then I get one hit only, and from this stack: 

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

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