Message-Id: <5.0.2.1.2.20011124192647.009e02e0@pop.gmx.net> X-Sender: martinSteuer AT gmx DOT de@pop.gmx.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 24 Nov 2001 19:51:36 +0100 To: djgpp AT delorie DOT com From: Martin Steuer Subject: Problems with gdb??? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Reply-To: djgpp AT delorie DOT com Hello to all, Please reply also directly to me. I've got the following problem, i've written my own Interrupt Wrapper so that i can get normal C Rountines called upon hardware interrupts. After debugging the wrapper and the function which i call to install a C Routine as the IRQ Handler my first test programs ran fine. So I moved on to code stuff where I need this IRQ Wrapper. 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. I know that RHIDE only uses gdb for debugging so i tried single stepping with gdb directly (i'm not very familiar with it though), and i got the same system crashes. When completly executing the program under gdb or RHIDE without using any breakpoints i got no problems (by the way i'm using gdb v5.0). So finally here's my question: Does anyone know about gdb having problems with hooked hardware interrupts? I hardly tried to find any problems in my wrapper but i can't see any, the program runs fine without being debugged. But it would also be very hard or even impossible to remove all Hardware Interrupt Handlers everytime before debugging. Thanks guys in advance, Martin