Date: Thu, 27 May 93 09:16:54 EDT
From: engdahl AT brutus DOT aa DOT ab DOT com (Jon Engdahl)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: source debug

I'm sure that I have seen source lines displayed by debug32 at one
time, but I can't figure out why it isn't working now. I am using 2.4.0
downloaded from omnigate, with go32 v1.09 compiled from sources with a
couple mods. I made sure that the -DSOURCE_LIST is set on the
compilation of debug32. I have a hunch that the problem is that the
compiler is not including the necessary info.  I tried objdump-ing
"hello.o" and "hello" (compiled with both -g and -g[0-3]) and I
couldn't see anything that looked like source line info. Can 2.4.0
generate the source debug info required by debug32? The sources,
objects, and executables are all in the current directory. Hmmm.. what
else could be wrong?

I found something odd when recompiling debug32 with mods - my new stuff
was so big that the code segment of debug32 was greater than 64K, but
bcc and tlink didn't complain. Obviously, the executable didn't run,
and it took a while to figure out why. This raises the question, can I
recompile go32 and debug32 using a different memory model? My hunch is
that the answer is "no", because the mapping of rcode onto the codeseg
will no longer be valid.

I remember seeing some talk about "spawn". Is there a mod to 1.09 that
implements the spawn functions? If not, I'll post mine. (I have fork
and exec mostly working. I call it a "plastic fork" - it actually
creates a thread, not a process. The point is to get make-3.65 and bash
working.)

Jonathan Engdahl, Sr. Project Engineer | engdahl AT aa DOT ab DOT com N8XVY 313-998-2450
Allen-Bradley Co.                      | A Rockwell International Company
555 Briarwood Circle,                  | Industrial Communication Networks
Ann Arbor, Michigan, 48108, USA        | system design, software, ASICs