Date: Sun, 14 Jun 1998 13:57:34 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: d-range! <d-range AT thefridge DOT vet DOT fnt DOT hvu DOT nl>
cc: djgpp AT delorie DOT com
Subject: Re: Debugger problem
In-Reply-To: <35819B3F.4F68E3A1@thefridge.vet.fnt.hvu.nl>
Message-ID: <Pine.SUN.3.91.980614135708.6294W-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 12 Jun 1998, d-range! wrote:

> Somewhere in my code I need to inspect whatever is at fs:0 but 'x/4bx
> $fs:0' produces a  parse error.

AFAIK, you cannot do that directly.  The easiest way to achieve this
is to link in a function such as `dosmemget' or `movedata' and call it
from GDB using the `call' command.  (If you need to look at FS:0,
chances are you already have `dosmemget' in your program.)

> Furthermore I happen to like the WATCOM debugger a lot, so I was
> wondering if there's a way to use it with DJGPP,

This is highly improbable.  The binary format used by DJGPP is
different from Watcom's, so the most you could hope for is to debug on
the machine instructions' level.

> or if there's an alike debugger for DJGPP, preferably also
> available for Linux.

GDB is of course available on Linux ;-).