X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
Date:	Thu, 10 Jan 2002 17:33:48 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	roland_asmann AT yahoo DOT com
Message-Id:	<2950-Thu10Jan2002173348+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp AT delorie DOT com
In-reply-to:	<20020110142219.39329.qmail@web9102.mail.yahoo.com> (message from
	ROLAND on Thu, 10 Jan 2002 06:22:19 -0800 (PST))
Subject:	Re: Problem with alarm & signal
References:	<20020110142219 DOT 39329 DOT qmail AT web9102 DOT mail DOT yahoo DOT com>
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

> Date: Thu, 10 Jan 2002 06:22:19 -0800 (PST)
> From: ROLAND <roland_asmann AT yahoo DOT com>
> 
> > Then post the full text of the message here, and
> > someone will help
> > you with the debugger.
> 
> Well, here it is...
> 
> The instruction at "0x0f00115e" referenced memory at
> "0xffffffff". The memory could not be "read".

Hmm... 0x0f00115e doesn't look like an address in a DJGPP program.
Can you load the program into GDB, like this:

    gdb foo.exe

and then type "disassmble 0x0f00115e", and see whether GDB finds that
address in the program?

> I also tried debugging with GDB, but something went
> wrong there... I've never worked with GDB before, so
> it could be my fault, but when the program crashed,
> GDB crashed too!

If the bug in the debuggee is hard enough, it could conceivably crash
the debugger as well, especially when the debuggee hooks hardware
interrupts.  It's not unheard of.

- Raw text -