darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

* remote-udi.c (udi_close, udi_detach, udi_kill): Add comments.

Browse source
This commit is contained in:
Jim Kingdon 1994-01-28 20:43:59 +00:00
parent 52fa9d667a
commit b09f44d2c9
2 changed files with 11 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gdb/ChangeLog
View file

@ -1,3 +1,7 @@
Fri Jan 28 15:40:33 1994 Jim Kingdon (kingdon@lioth.cygnus.com)
* remote-udi.c (udi_close, udi_detach, udi_kill): Add comments.
Fri Jan 28 11:55:52 1994 Rob Savoye (rob@darkstar.cygnus.com)
* configure.in: Make m68k-coff and aout add monitor support in

9
gdb/remote-udi.c
View file

@ -360,8 +360,11 @@ udi_detach (args,from_tty)
if (UDIDisconnect (udi_session_id, UDIContinueSession))
error ("UDIDisconnect() failed in udi_detach");
pop_target(); /* calls udi_close to do the real work */
/* calls udi_close to do the real work (which looks like it calls
UDIDisconnect with UDITerminateSession, FIXME). */
pop_target();
/* FIXME, message too similar to what udi_close prints. */
if (from_tty)
printf_unfiltered ("Ending remote debugging\n");
}
@ -1011,7 +1014,9 @@ just invoke udi_close, which seems to get things right.
#endif /* 0 */
/* Keep the target around, e.g. so "run" can do the right thing when
we are already debugging something. */
we are already debugging something. FIXME-maybe: should we kill the
TIP with UDIDisconnect using UDITerminateSession, and then restart
it on the next "run"? */
inferior_pid = 0;
}