This is the mail archive of the insight@sourceware.cygnus.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Insight debugging remote targets


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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]