public inbox for
help / color / mirror / Atom feed
Subject: insight/328: Remote debugging - register window does not get updated after download
Date: Thu, 14 Feb 2008 23:33:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         328
>Category:       insight
>Synopsis:       Remote debugging - register window does not get updated after download
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 14 23:33:01 UTC 2008
>Release:        GNU gdb 6.7.1
cygwin_NT-5.1 1.5.25(0.156/4/2)
Here is my setup:
I have built an arm-elf-insight under cygwin. 
I have an arm-9-core to that I connect the arm-elf-insight via TCP/IP (over the Segger JLink GDB Server). 

Here is what I do:
I start my segger gdb server.
I start my arm-elf-insight debugger.
I load my axf (which is the ARM ELF) file into the debugger (with "file" "open").
I open the register window.
I connect to the target. 
Now the registers are read from the target (and the reg PC is set e.g. to 0x18).
I download the axf file to the target (part of the AXF file is the entry point).

Now the reg PC is not updated to the entry point in the register window. However if I read the PC value directly in the console window it is set to the entry point. 
Shouldn't the register window be updated after a download?



             reply	other threads:[~2008-02-14 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 23:33 [this message]
2008-02-21  1:31 kseitz
2008-02-21 10:43 Arpa Monika
2008-02-22  9:23 Arpa Monika
2009-11-16 12:23 Robert Bu

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).