Date:	Thu, 14 Oct 1999 13:20:02 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Wendy E. McCaughrin" <wemccaug AT prairienet DOT org>
cc:	djgpp AT delorie DOT com
Subject:	Re: formats accepted by fsdb
In-Reply-To:	<uwfN3.575$_9.41@firefly>
Message-ID:	<Pine.SUN.3.91.991014131421.26916A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 14 Oct 1999, Wendy E. McCaughrin wrote:

>  What file formats are accepted by the debuggers fsdb and edebug32?

There can be two questions here, and I don't know which one are you 
asking, so I will answer both.

The DJGPP debug support, used by *all* the debuggers, not only FSDB and 
EDEBUG32, can only load a COFF executable, either raw COFF or COFF with 
the DJGPP stub.  This is one question.

The other question you might have been asking is what format of the debug 
info is supported.  The answer to that is: FSDB and EDEBUG32 support COFF 
debug format only (they also support a.out, but that's not relevant for 
DJGPP v2.x), while GDB and RHIDE support COFF and stabs.

>  I have assembled a nasm program under each of the possible formats
>  and none can be loaded by either utility. E.g., I nasm'd the pro-
>  gram with -f coff and then did: coff2exe on it, but the .exe fail-
>  ed to load.

Please post the details: the precise command line you used to produce the 
executable, how did you invoke the debugger, and what was the error 
message printed by the debugger.

Also, did you make sure that the program can run (outside the debugger)?  
Perhaps you only produced an object file, not an executable program (your 
description above doesn't say anything about linking the program).

- Raw text -