Date: Wed, 13 Jun 2001 10:19:42 -0400
Message-Id: <200106131419.KAA00731@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <20010613090341.B25907@kendall.sfbr.org> (message from JT
	Williams on Wed, 13 Jun 2001 09:03:41 -0500)
Subject: Re: fsdb and .exe files from djasm
References:  <20010613090341 DOT B25907 AT kendall DOT sfbr DOT org>
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


> 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).

fsdb is a 32-bit p-mode debugger and djasm produces 16-bit r-mode
code.  Do you really expect this to work?

In general, *any* debugger is going to have problems debugging code
that switches CPU modes.  You really need an ICE to debug those (and
there have been many times I wish I had one) or at least a chip
simulator.