Date: Wed, 13 Jun 2001 18:49:36 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: JT Williams <jeffw AT darwin DOT sfbr DOT org>
cc: djgpp-workers AT delorie DOT com
Subject: Re: fsdb and .exe files from djasm
In-Reply-To: <20010613090341.B25907@kendall.sfbr.org>
Message-ID: <Pine.SUN.3.91.1010613184816.19790D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 13 Jun 2001, JT Williams wrote:

> I am surprised to find that I cannot use fsdb to step through stub.exe,
> or any other djasm-generated .exe file.  I suspect fsdb is gagging on some
> aspect of djasm's exe header, but this is mostly a guess.  Can anyone
> shed some light on this?  It seems desirable for djasm to generate .exe
> files that behave as .exe files should (whatever that might be).

You can use DOS's DEBUG intil the point where the stub switches to 
protected mode.  Between that point and crt0.S's entry point, we don't 
have any solution in DJGPP.