public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-17384-4717-hTYgDFTryw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17384-4717@http.sourceware.org/bugzilla/>
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.
next prev parent reply other threads:[~2014-09-23 9:23 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
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 [this message]
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-hTYgDFTryw@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: link
Be 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).