From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <200106151655.SAA21747@mother.ludd.luth.se>
Subject: Re: Debugging on 386 (fwd)
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Fri, 15 Jun 2001 18:55:06 +0200 (MEST)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Another one that somehow petered out.

Forwarded message:
> According to Eli Zaretskii:
> > Could you try doing the same in FSDB?  I'd like to establish if this
> > has anything to do with GDB's own code.
> 
> I can't get past the first exception 7 at 0x5535 (fstcw [esp]) it
> seems. It doesn't matter if I have a breakpoint at main or not.
> 
> > Note that FSDB uses hardware-assisted breakpoints for the first 4
> > breakpoints, so for a fair comparison either use hbr in GDB or put 4
> > watchpoints on some random data in FSDB, so that the debug registers
> > are taken, before you put your breakpoint.  (Actually, both variations
> > are probably worth trying, in case using hbr in GDB somehow solves the
> > problem, or at least produces a different effect that could give some
> > insight.)
> 
> It seems it doesn't matter if I use hardware breakpoints or not.
> 
> Futhermore, if I do "handle SIGEMT nostop noprint; br main; r, n, n" I
> get an endless loop of "Exiting due to signal SIGFPE". Again it
> doesn't matter if I use hardware break points or not.


Right,

						MartinS