To:	dj AT ctron DOT com (DJ Delorie)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Source listings and debuggers
Return-Receipt-To:	peter AT deakin DOT edu DOT au
Date:	Mon, 11 Apr 94 09:46:07 +1000
From:	Peter Horan <peter AT deakin DOT edu DOT au>

	>Date: Fri, 8 Apr 94 14:57:12 -0400
	>From: dj AT ctron DOT com (DJ Delorie)

	>> Is it possible to get the source code listings along with the
	>> assembler listings? What I have tried is
	>>
	>> gcc -g -o test test.c
	>> go32 -d gdb test
	>> go32 -d fsdb test
	>> go32 -d edebug32 test
	>
	>Hmmm... this is what I do, so it *should* work.  Try building the .o
	>separate from the executable, maybe it will work better (?).  Note
	>that edebug *always* prints the assembler (fsdb also), but with -g
	>will *also* print the source lines, if the source file is in the
	>current directory.
The source lines are not always shown. I have not yet noticed any
consistency about when they appear and when they do not. I use a
makefile which compiles the object files separately. I had
discovered the current directory factor and exploited that, but
otherwise, source sometimes appears and sometimes not. It's
annoying more than anything.

Peter Horan                     School of Computing and Mathematics
peter AT deakin DOT edu DOT au	   	Deakin University
                                Geelong
+61-52-27 1234 (Voice)          Victoria 3217
+61-52-27 2028 (FAX)            Australia

- Raw text -