From:	"John S. Fine" <johnfine AT erols DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: GDB to debug Masm/Nasn output?
Date:	Sun, 21 Feb 1999 15:33:18 -0500
Lines:	25
Message-ID:	<36D06D8E.40D4@erols.com>
References:	<rmo4sDAOKxz2Ewuu AT xemu DOT demon DOT co DOT uk>
	<36cf4632 DOT 80880437 AT news DOT cso DOT uiuc DOT edu> <JRIAhXANt2z2Ew4H AT xemu DOT demon DOT co DOT uk>
Mime-Version:	1.0
X-Trace:	gjJ+ogTWDe2zKY/XyZyZ3pSeMAaMJ+l87yvwNWjQXw8=
X-Complaints-To:	abuse AT rcn DOT com
NNTP-Posting-Date:	21 Feb 1999 20:34:37 GMT
X-Mailer:	Mozilla 3.01 (Win95; U)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Dave Bird wrote:

> >>  Can I debug MASM (or NASM) output with GDB or similar?  I can't use
. . .
>  OK, I'll get NASM, as that seems a fairly straightforward solution.

  NASM can generate output in DJGPP COFF format or Microsoft COFF
format (or several other formats).  You can link NASM's (DJGPP)
COFF format using LD and debug it with GDB, but there is a
big problem:

  I don't think NASM can generate debug information that GDB
can read, so you will be debugging without links back to the
source files and without local symbols (I am not sure whether
GDB can even find global symbols under these conditions).

  To get debugging info in NASM output at all, you need a
prerelease of version 0.98 (see my web page).  With that,
I *think* all you get is Borland compatible debug info in
OBJ format (that David Lindauer and I added).  Someone was
talking about putting GDB compatible debug info in as well,
but I don't think it ever happened.
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/

- Raw text -