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:03:00 -0000 [thread overview] Message-ID: <bug-17384-4717-zDVhqYX61I@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17384-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17384 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves <palves at redhat dot com> --- Pasting "http://temp.minimum.se/bt_for_memory_error.txt" here, for easier reference, and so we're protected against that resource disappearing in the future: #0 memory_error_message (err=err@entry=TARGET_XFER_E_IO, gdbarch=0x1ed4cc0, memaddr=memaddr@entry=1) at corefile.c:196 #1 0x000000000058bd1d in memory_error (err=TARGET_XFER_E_IO, memaddr=memaddr@entry=1) at corefile.c:224 #2 0x000000000058be11 in read_memory (memaddr=1, myaddr=myaddr@entry=0x7fff5dee86d0 "\377\200\203R", len=len@entry=4) at corefile.c:261 #3 0x000000000058bec5 in read_memory_integer (memaddr=<optimized out>, len=4, byte_order=BFD_ENDIAN_LITTLE) at corefile.c:357 #4 0x000000000058bf02 in do_captured_read_memory_integer (data=data@entry=0x7fff5dee8770) at corefile.c:322 #5 0x0000000000513225 in catch_errors (func=func@entry=0x58bef0 <do_captured_read_memory_integer>, func_args=func_args@entry=0x7fff5dee8770, errstring=errstring@entry=0x6c20cd "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:237 #6 0x000000000058be8b in safe_read_memory_integer (memaddr=<optimized out>, len=len@entry=4, byte_order=byte_order@entry=BFD_ENDIAN_LITTLE, return_value=return_value@entry=0x7fff5dee87b8) at corefile.c:343 #7 0x000000000041122a in arm_scan_prologue (cache=0x1e51ec0, this_frame=0x1e51e00) at arm-tdep.c:1996 #8 arm_make_prologue_cache (this_frame=0x1e51e00) at arm-tdep.c:2022 #9 0x000000000041142a in arm_prologue_this_id (this_frame=0x1e51e00, this_cache=0x1e51e18, this_id=0x1e51e60) at arm-tdep.c:2052 #10 0x00000000005e4ea4 in compute_frame_id (fi=0x1e51e00) at frame.c:459 #11 get_prev_frame_if_no_cycle (this_frame=this_frame@entry=0x1e51470) at frame.c:1781 #12 0x00000000005e72ca in get_prev_frame_always_1 (this_frame=0x1e51470) at frame.c:1955 #13 get_prev_frame_always (this_frame=0x1e51470) at frame.c:1972 #14 0x00000000005e7754 in frame_unwind_caller_id (next_frame=<optimized out>) at frame.c:500 #15 0x0000000000503a07 in process_event_stop_test (ecs=ecs@entry=0x7fff5dee9070) at infrun.c:4738 #16 0x0000000000505478 in handle_inferior_event (ecs=0x7fff5dee9070) at infrun.c:3424 #17 0x00000000005079ba in fetch_inferior_event (client_data=client_data@entry=0x0) at infrun.c:2899 #18 0x000000000051dc73 in inferior_event_handler (event_type=INF_REG_EVENT, client_data=0x0) at inf-loop.c:58 #19 0x0000000000428fce in run_async_handler_and_reschedule (scb=0x1ec5600) at ser-base.c:137 #20 0x000000000051bf73 in process_event () at event-loop.c:340 #21 0x000000000051c2c7 in gdb_do_one_event () at event-loop.c:404 #22 0x000000000051c4e7 in start_event_loop () at event-loop.c:429 #23 0x0000000000515b73 in captured_command_loop (data=data@entry=0x0) at main.c:322 #24 0x0000000000513225 in catch_errors (func=func@entry=0x515b60 <captured_command_loop>, func_args=func_args@entry=0x0, errstring=errstring@entry=0x6c20cd "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:237 #25 0x0000000000516a76 in captured_main (data=data@entry=0x7fff5dee93c0) at main.c:1142 #26 0x0000000000513225 in catch_errors (func=func@entry=0x516060 <captured_main>, func_args=func_args@entry=0x7fff5dee93c0, errstring=errstring@entry=0x6c20cd "", mask=mask@entry=RETURN_MASK_ALL) at exceptions.c:237 #27 0x0000000000516f1b in gdb_main (args=args@entry=0x7fff5dee93c0) at main.c:1150 #28 0x0000000000407b65 in main (argc=<optimized out>, argv=<optimized out>) at gdb.c:32 -- 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:03 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 [this message] 2014-09-16 9:16 ` palves at redhat dot com 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-zDVhqYX61I@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: linkBe 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).