www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2001/11/24/14:31:45

Date: Sat, 24 Nov 2001 21:29:31 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Martin Steuer <martinSteuer AT gmx DOT de>
Message-Id: <1858-Sat24Nov2001212931+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: <5.0.2.1.2.20011124192647.009e02e0@pop.gmx.net> (message from
Martin Steuer on Sat, 24 Nov 2001 19:51:36 +0100)
Subject: Re: Problems with gdb???
References: <5 DOT 0 DOT 2 DOT 1 DOT 2 DOT 20011124192647 DOT 009e02e0 AT pop DOT gmx DOT net>
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: Sat, 24 Nov 2001 19:51:36 +0100
> From: Martin Steuer <martinSteuer AT gmx DOT de>
> 
> I got some problems and tried to debug the program under RHIDE (v 1.4.9).
> BUT single stepping thru this program was nearly impossible after my IRQ 
> Handler had been installed -- the debugging sessions crashed very often the 
> whole system.

If the crashes are accompanied by the normal DJGPP crash message with
registers and EIP traceback, please post here one of these messages
in its entirety.

> So finally here's my question: Does anyone know about gdb having problems 
> with hooked hardware interrupts?

Please tell more details; it's hard to answer that question because
it's too general.  Debugging programs that hook hardware interrupts
is a bit tricky, but should in general work.

To give a more specific answer, we need to know what hardware
interrupts does your program hook, and how (in protected mode, real
mode, or both).  A source of your wrapper function might be useful.
Also, what version of which OS is that?  Finally, if you don't use
DJGPP v2.03, such problems are expected, so please upgrade.

Oh, and of course, the usual gotchas of hooking hardware interrupts
apply even under a debugger, so please make sure you lock all the
memory, including the stack, used by code that is called in the
interrupt context.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019