Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Girish Shilamkar <girish@linsyssoft.com>
To: gdb@sources.redhat.com
Subject: Invalid update to pc in instruction
Date: Tue, 28 Mar 2006 14:34:00 -0000	[thread overview]
Message-ID: <1143537953.4865.6.camel@krypton> (raw)

Hi,
	While running kgdb kernel I got following error:

(gdb) p/x $pc
$4 = 0xc00ef530
(gdb) n
0xc00ef530 in memcpy () at uaccess.h:363
363     in uaccess.h
Invalid update to pc in instruction
(gdb) disas $pc
Dump of assembler code for function memcpy:
0xc00ef520 <memcpy+0>:  stmdb   sp!, {r0, r4, lr}
0xc00ef524 <memcpy+4>:  subs    r2, r2, #4      ; 0x4
0xc00ef528 <memcpy+8>:  blt     0xc00ef5dc <memcpy+188>
0xc00ef52c <memcpy+12>: ands    r12, r0, #3     ; 0x3
0xc00ef530 <memcpy+16>: pld     [r1]
0xc00ef534 <memcpy+20>: bne     0xc00ef5fc <memcpy+220>
0xc00ef538 <memcpy+24>: ands    r12, r1, #3     ; 0x3
0xc00ef53c <memcpy+28>: bne     0xc00ef62c <memcpy+268>


I am using cross gdb-6.4 for Intel PXA270 (armv5l) processor.
Kindly let me know in what scenario does the error msg "Invalid update
to pc in instruction" is displayed ?

Thanks & Regards,
-Girish.




             reply	other threads:[~2006-03-28  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 14:34 Girish Shilamkar [this message]
2006-03-28 15:20 ` Daniel Jacobowitz

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=1143537953.4865.6.camel@krypton \
    --to=girish@linsyssoft.com \
    --cc=gdb@sources.redhat.com \
    /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