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: Thu, 09 Oct 2014 08:10:00 -0000	[thread overview]
Message-ID: <bug-17384-4717-yAInQBTMA9@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 #26 from Yao Qi <qiyao at gcc dot gnu.org> ---
(In reply to molsson from comment #24)

I've got a small case which has such stub,

   0x20011ce <main+33558534>:   blx     0x20011d8
   0x020011d2 <main+33558538>:  00 23   movs    r3, #0
   ...
   ...
   0x20011d8:   ldr     r12, [pc, #4]   ; 0x20011e4
   0x20011dc:   add     r12, pc, r12
   0x20011e0:   bx      r12

 but GDB behaves correctly.

infrun: stop_pc = 0x20011d8^M
infrun: stepped into subroutine^M
infrun: inserting step-resume breakpoint at 0x20011d2^M
infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread
[Thread 1] at 0x20011d8^M
infrun: prepare_to_wait^M
infrun: target_wait (-1, status) =^M
infrun:   42000 [Thread 1],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: infwait_normal_state^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: stop_pc = 0x20011d2^M
infrun: BPSTAT_WHAT_STEP_RESUME^M
infrun: stepped to a different line^M
infrun: stop_waiting^M
14        return 0;

so I want to see your log.

> 
> Breakpoint 1, blink::RenderFullScreen::createPlaceholder (this=0x7f038100,
> style=..., frameRect=...) at
> ../../third_party/WebKit/Source/core/rendering/RenderFullScreen.cpp:188
> 188	    if (style->width().isAuto())
> (gdb) n
> 0x7a6f4ac0 in ?? () from
> /media/ssd/src/opera/opera/chromium/src/out_generic_armv7/Debug/lib/
> libblink_web.cr.so

before type command "n", please do "set debug infrun 1".  Copy the output here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-16804-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu Oct 09 13:31:47 2014
Return-Path: <gdb-prs-return-16804-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 16357 invoked by alias); 9 Oct 2014 13:31:47 -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
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 16274 invoked by uid 48); 9 Oct 2014 13:31:45 -0000
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17471] repeating a background command makes it foreground
Date: Thu, 09 Oct 2014 13:31: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: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: palves at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: palves at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-17471-4717-8zkxHhZc9w@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17471-4717@http.sourceware.org/bugzilla/>
References: <bug-17471-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-q4/txt/msg00047.txt.bz2
Content-length: 524

https://sourceware.org/bugzilla/show_bug.cgi?id\x17471

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at sourceware dot org   |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
Mine.

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


  parent reply	other threads:[~2014-10-09  8:10 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
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 [this message]
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-yAInQBTMA9@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).