public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: Robert Bu <robert_bu@realsil.com.cn> To: kseitz@sources.redhat.com Cc: insight-prs@sources.redhat.com, Subject: Re: insight/328: Remote debugging - register window does not get updated after download Date: Mon, 16 Nov 2009 12:23:00 -0000 [thread overview] Message-ID: <20091116122301.6596.qmail@sourceware.org> (raw) The following reply was made to PR insight/328; it has been noted by GNATS. From: Robert Bu <robert_bu@realsil.com.cn> To: <insight-gnats@sources.redhat.com> Cc: Subject: Re: insight/328: Remote debugging - register window does not get updated after download Date: Mon, 16 Nov 2009 20:14:49 +0800 Hi, I have the same problem here (insight 6.8-1). I can see the updated registers if I select another group, such as "system". However, the register remain as read-only. They become editable only after I run some instructions. And if I connect to remote target first, then open the register window, all works right. I think it can be reproduced by gdbserver. If I open the register window first, then connect to the remote target (through "target remote xxx" in console window), the register shown in insight's register window is read-only. However, if I connect to the remote target first, then open the register window, all seems OK. And in the former problematic situation, if I close the register windown, then open it again, it's also OK. Maybe, there's some event missing for the register window. -- Best regards. Robert
next reply other threads:[~2009-11-16 12:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-16 12:23 Robert Bu [this message] -- strict thread matches above, loose matches on Subject: below -- 2008-02-22 9:23 Arpa Monika 2008-02-21 10:43 Arpa Monika 2008-02-21 1:31 kseitz 2008-02-14 23:33 monika.arpa
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=20091116122301.6596.qmail@sourceware.org \ --to=robert_bu@realsil.com.cn \ --cc=insight-prs@sources.redhat.com \ --cc=kseitz@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: linkBe 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).