From: Keith Seitz <kseitz@firetalk.com>
To: fnasser@cygnus.com, jingham@apple.com
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight debugging remote targets
Date: Fri, 23 Jun 2000 06:00:00 -0000 [thread overview]
Message-ID: <39535F1D.FEFC1DEE@firetalk.com> (raw)
In-Reply-To: <17CE01D4.2D92A92E.00A463D9@cs.com>
mwcruess@cs.com wrote:
>
> Thanks for the information. The code that I am
> modifying uses monitor.c. Around monitor.c line 2250
> there is code:
>
> if (exec_bfd)
> write_pc (bfd_get_start_address (exec_bfd));
>
> inferior_pid = 0; /* No process now */
>
Hmmmm... I would guess that this is incorrect, but it looks like it has
been this way for some time. I am a little confused, though, since I
remember using Insight on several monitors: mon2000 (m32r) and picobug
(mcore).
How did it ever work? I see the same thing happen in dink32-rom.c,
m32r-rom.c, dve3900-rom.c, mon960-rom.c, and almost all remote targets
(remote-*.c).
Anyone remember how this is supposed to work?
Keith
next prev parent reply other threads:[~2000-06-23 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-22 5:07 MWCruess
2000-06-22 6:04 ` Keith Seitz
2000-06-22 15:35 ` mwcruess
2000-06-23 6:00 ` Keith Seitz [this message]
2000-06-22 6:11 ` Fernando Nasser
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=39535F1D.FEFC1DEE@firetalk.com \
--to=kseitz@firetalk.com \
--cc=fnasser@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@apple.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).