From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-id: <39535F1D.FEFC1DEE@firetalk.com>
References: <6c.6d4c22.26835b76@cs.com> <39520ECE.79E7DADF@firetalk.com> <17CE01D4.2D92A92E.00A463D9@cs.com>
X-SW-Source: 2000-q2/msg00326.html

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