X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f Message-ID: <20020110162441.98731.qmail@web9106.mail.yahoo.com> Date: Thu, 10 Jan 2002 08:24:41 -0800 (PST) From: ROLAND Subject: Re: Problem with alarm & signal To: djgpp AT delorie DOT com Cc: eliz AT is DOT elta DOT co DOT il In-Reply-To: <2950-Thu10Jan2002173348+0200-eliz@is.elta.co.il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Precedence: bulk --- Eli Zaretskii wrote: > 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 did that, and GDB said something like: No function at specified address So I guess this didn't help either... BTW, Do I need to put the PMCOM source in this dir as well? I just put in the .a file, but maybe it needs the sources as well... > 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. Is there a way to solve this? I tried something different now, I first opened the program in GDB and typed run, and then the program crashed. Now I set a breakpoint, and run again, and then used step from the breakpoint on. At that point everything seemed to go allright. After having used step for a number of times (I was in a while-loop) I decided to let the program continue, so it maybe ran into the bug somewhere. The strangest thing then was, that the program didn't crash! As if the bug had not been there. Off course when I pressed CTRL-C, it happened again, but it did not occur at runtime! __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/