From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3309 invoked by alias); 16 Sep 2014 09:16:53 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 3243 invoked by uid 48); 16 Sep 2014 09:16:52 -0000 From: "palves at redhat dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q3/txt/msg00606.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17384 --- Comment #3 from Pedro Alves --- 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=, #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.