public inbox for email@example.com help / color / mirror / Atom feed
From: "Arpa Monika" <Monika.Arpa@austriamicrosystems.com> To: firstname.lastname@example.org Cc: email@example.com, Subject: RE: insight/328: Remote debugging - register window does not get updated after download Date: Fri, 22 Feb 2008 09:23:00 -0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) The following reply was made to PR insight/328; it has been noted by GNATS. From: "Arpa Monika" <Monika.Arpa@austriamicrosystems.com> To: <email@example.com>, <firstname.lastname@example.org>, "Arpa Monika" <Monika.Arpa@austriamicrosystems.com>, <email@example.com>, <firstname.lastname@example.org> Cc: Subject: RE: insight/328: Remote debugging - register window does not get updated after download Date: Fri, 22 Feb 2008 10:18:06 +0100 Hello! I tried also the "run" button. This is not really an improvement. Here is what it does: 1. Connect to the remote target. 2. Download the axf-File to the target. 3. Immediatly start execution on the target - <<<<<<<<<<< that is not what I want. 4. Stop at the first breakpoint that I have set. 5. Show the appropriate source file, and registers. 6. Show that the program is not running anymore - <<<<<<<<<<< <that is not what I want. 7. To make it accept any new "step", "next", etc commands I need to click on "Connect to target" again. - Although the GDB-Server still shows that it is connected.=20 So using the run button does not help me.=20 Best regards, Monika > -----Original Message----- > From: email@example.com [mailto:firstname.lastname@example.org]=20 > Sent: Thursday, February 21, 2008 2:32 AM > To: email@example.com;=20 > firstname.lastname@example.org; Arpa Monika; email@example.com > Subject: Re: insight/328: Remote debugging - register window=20 > does not get updated after download >=20 > Synopsis: Remote debugging - register window does not get=20 > updated after download >=20 > Responsible-Changed-From-To: unassigned->kseitz > Responsible-Changed-By: kseitz > Responsible-Changed-When: Thu Feb 21 01:31:32 2008 > Responsible-Changed-Why: > mine > State-Changed-From-To: open->analyzed > State-Changed-By: kseitz > State-Changed-When: Thu Feb 21 01:31:32 2008 > State-Changed-Why: > Yeah, that sounds like a problem. I'll bet an event is=20 > not being properly generated when after the attach and/or=20 > download happens. > =20 > Alas, it's been so long since I've used an embedded=20 > target with gdb, that I don't exactly remember how all this=20 > is supposed to work (e.g., where exactly the event is=20 > supposed to get generated)... > =20 > Before I make some suggestions on how to fix this, I need=20 > a little more information: Are you using the Run button to do=20 > all of this, or are you using either the console window=20 > (typing "target ..." and "load") or the Run menu options? I=20 > *think* that if you use the Run button, this should work.=20 > I'll bet it does not work for the other cases because of the=20 > command-line/GUI disconnect from which Insight suffers. >=20 > http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-tra il&database=3Dinsight&pr=3D328 >=20
next reply other threads:[~2008-02-22 9:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-22 9:23 Arpa Monika [this message] -- strict thread matches above, loose matches on Subject: below -- 2009-11-16 12:23 Robert Bu 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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).