Date:	Mon, 12 Jun 2000 15:36:57 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
cc:	garyroughton AT netzero DOT net, djgpp AT delorie DOT com
Subject:	Re: Need help with FSDB/EDEBUG32 before I lose my mind
In-Reply-To:	<Pine.LNX.4.21.0006120413100.841-100000@roadrunner.grendel.net>
Message-ID:	<Pine.SUN.3.91.1000612153632.5082I-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 12 Jun 2000, Kalum Somaratna aka Grendel wrote:

> > D:\djgpp>fsdb hello
> > hello: No such file or directory (ENOENT)
> > Load failed for image lines
> > 
> > What then is "debug-image", if not the executable?
> 
> Yes it is in the executable, but please specify the *full name* of the
> executable, hello.exe *not* just hello...
> 
> ie fsdb hello.exe will work.

Actually, even "fsdb hello" will work, provided that there is a file
`hello' in that directory.  But many users say "gcc -o hello.exe",
which only creates `hello.exe'.  If you say "gcc -o hello", that would
produce both `hello' and `hello.exe', and "fsdb hello" will work.

Note that chapter 12 in the FAQ explicitly tells you to say "gdb foo.exe".

> I know it might seem stupid that a dos  debugger doesn't do this itself

Patches to fsdb to make it look for .exe are welcome.

- Raw text -