Mail Archives: djgpp/2005/08/26/07:46:05
Radical NetSurfer <RadSurfer AT yahoo DOT com> wrote:
> Someone suggested I examine the -S output to see what DJGPP
> is really putting in there for inport/outport; and do the same for
> Borland 16, and try to determine whats actually happening.
> I am aware of no real-time debugger for Borland 16 except through
> the IDE which I only rarely use.
Huh? What would a real-time debugger have to do with inspecting the
machine code? BCC doesn't usually go through assembly, i.e. it doesn't
have a direct equivalent of the -S switch. But that doesn't mean you
need a debugger to inspect machine code: tdump of the .obj file will
do just fine.
But yes, even 16-bit Borland has a stand-alone debugger. It's
unsurprisingly called "Turbo Debugger", and comes in several separate
flavours, depending on the platform you're running from, and the kind
of application you're trying to debug.
> I was thinking 32-bit mode vs. 16-bit mode somehow influences how
> inport/outport react/operate,
It most certainly does.
Another thing to watch out for is that these are 16-bit port accesses.
That's a somewhat shady area of the PC design, IIRC. Most gadgets
make do with 8-bit port access.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -