From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-16733-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 5278 invoked by alias); 23 Sep 2014 09:23:58 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 5241 invoked by uid 48); 23 Sep 2014 09:23:57 -0000
From: "qiyao at gcc dot gnu.org" <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, 23 Sep 2014 09:23: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: qiyao at gcc dot gnu.org
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: <bug-17384-4717-hTYgDFTryw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17384-4717@http.sourceware.org/bugzilla/>
References: <bug-17384-4717@http.sourceware.org/bugzilla/>
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/msg00722.txt.bz2

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

--- Comment #23 from Yao Qi <qiyao at gcc dot gnu.org> ---
(In reply to molsson from comment #17)

> Also, I can put a breakpoint on certain other functions like for example
> base::debug::TaskAnnotator::RunTask() and there I can use "next" without
> problems so there seems to be something special with
> blink::RenderFullScreen::createPlaceholder() or possibly with one of the
> functions it calls. Maybe something with inlining, or maybe because it's
> static, not sure.
> 

molsson,
Is your problem that can't use "next" in function
blink::RenderFullScreen::createPlaceholder()?  What is the output and message
of GDB?  You mixed your analysis and the problem report together, it makes
harder to understand what the problem is.

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