public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: julien.lincy@thomson.net
Cc: gdb-gnats@sources.redhat.com
Subject: pending/2542: Re: ARM single step problem with instruction 0xa5ffffeb
Date: Wed, 22 Oct 2008 13:08:00 -0000	[thread overview]
Message-ID: <20081022130006.GY14714@caradoc.them.org> (raw)
In-Reply-To: <20081022114101.8603.qmail@sourceware.org>


>Number:         2542
>Category:       pending
>Synopsis:       Re: ARM single step problem with instruction 0xa5ffffeb
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Wed Oct 22 13:08:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 On Wed, Oct 22, 2008 at 11:41:01AM -0000, julien.lincy@thomson.net wrote:
 > >Description:
 > I have a problem single stepping with a simple C program on ARM, with the instruction 0xa5ffffeb.
 > 
 > 8538:       a5ffffeb        ldrgeb  pc, [pc, #4075]!        ; 952b <__clz_tab+0x6b>
 > 
 > GDB stops with the error "Invalid update to pc in instruction".
 > 
 > The C program i'm trying to test is attached.
 > The ARM I use is an ARM v1136 (a bit specific...).
 
 I think there's something wrong with your environment.  That's not a
 valid instruction; PC is always aligned, so pc+4075 is unaligned.
 The middle of __clz_tab doesn't have function pointers in it.  And you
 can't do PC-relative loads with writeback.
 
 GDB is right to complain about that instruction.
 
 -- 
 Daniel Jacobowitz
 CodeSourcery
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


      reply	other threads:[~2008-10-22 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 11:48 gdb/2541: " julien.lincy
2008-10-22 13:08 ` Daniel Jacobowitz [this message]

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=20081022130006.GY14714@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-gnats@sources.redhat.com \
    --cc=julien.lincy@thomson.net \
    /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).