From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31394 invoked by alias); 26 Oct 2012 18:38:21 -0000 Received: (qmail 31373 invoked by uid 48); 26 Oct 2012 18:38:21 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/9310] nexti command does not work when debugging ARM assembly language Date: Fri, 26 Oct 2012 18:38: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-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 7.5 X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-q4/txt/msg00151.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=9310 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #2 from Pedro Alves 2012-10-26 18:38:19 UTC --- ARM or Thumb? A fix went in on 2012-08-22, for Thumb 'bx pc' and 'blx pc'. Otherwise, it may be simpler if you could debug this. Here's how. Debug the arm gdb with the host's (x86, I presume) gdb. On the (arm/android) gdb, and put a breakpoint on that particular bl instruction's address, and run to it (b *0xADDR; c). Then, on the top (x86) gdb, set a breakpoint on arm_get_next_pc, and let the android gdb continue. Tell the android GDB to continue the android program as well. arm_get_next_pc will be hit. This is the function that computes where the execution will land next, so GDB can put a breakpoint there, so that the android program executes only one instruction (is single-stepped). The symptom of the bug usually means that for some reason this computing the next pc goes wrong. It's usually evident whether the computed address looks reasonable or not. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.