🚀 go-pugleaf

I've been trying to figure out how I would use gdb with an ICE to do remote
debugging. So far, I've noticed a couple of things:

1) It appears that gdb knows deep in its bones that once the target program is
started (with a run, continue, next, etc), that nothing else (except QUIT) can
happen. The ICE has no such restriction. I'd like to be able to continue to
examine (static) variables, browse source, set breaks, etc. after I start the
target program. Anyone have any opinions about how much trouble I'm going to
have "removing" this "hang until target stops" from gdb, if it even possible
or if somebody has already done it. (Detach doesn't do the trick since it
removes all breakpoints in the process).

2) I don't completely understand this comment found in symtab.h:

/* ...
   Each item used to be an int; either minus a line number, or a
   program counter.  If it represents a line number, that is the line
   described by the next program counter value.  If it is positive, it
   is the program counter at which the code for the next line starts.  */
     
struct linetable_entry
{
  int line;
  CORE_ADDR pc;
};

Does this mean one cannot run executables in a 32 bit address space above
location 0x7FFFFFFF or does this comment no longer apply?

Thanks in advance. Reply to shepperd@netcom.com or shepperd@agames.com
-- 
Dave Shepperd.                             agames.com!shepperd
Atari Games Corporation, 675 Sycamore Drive, Milpitas CA 95035.
Nobody knows what I'm saying. I don't even know what I'm saying.