From: pavenis AT lanet DOT lv
Message-ID: <B0000088084@stargate.astr.lu.lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Tue, 25 May 1999 11:43:08 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: gdb 4.18 for DJGPP (alpha)
References: <B0000087946 AT stargate DOT astr DOT lu DOT lv>
In-reply-to: <Pine.SUN.3.91.990524161540.7396E-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.11)
Reply-To: djgpp-workers AT delorie DOT com

On 24 May 99, at 16:17, Eli Zaretskii wrote:

> 
> On Mon, 24 May 1999 pavenis AT lanet DOT lv wrote:
> 
> > > 	{
> > > 	  if (a_tss.tss_irqn == sig_map[i].go32_sig)
> > > 	    {
> > > #if __DJGPP_MINOR__ < 3
> > > 	      if ((status->value.sig = sig_map[i].gdb_sig) !=
> > > 		  TARGET_SIGNAL_TRAP)
> > > 		status->kind = TARGET_WAITKIND_SIGNALLED;
> > > #else
> > >         status->value.sig = sig_map[i].gdb_sig;
> > >         status->kind = TARGET_WAITKIND_STOPPED;
> > > #endif
> > > 	      break;
> > > 	    }
> > > 	}
> > > 
> > > if I enable the v2.03 part, breakpoints stop working (GDB says the
> > > program got SIGTRAP instead), and if I enable the v2.02 part, Ctrl-C
> > > kills the debuggee, like with the old dbgcom.c
> > 
> > Of course. GDB gets TARGET_WAITKIND_SIGNALLED that is 
> > command to kill debugee. We should have 
> > TARGET_WAITKIND_STOPPED to avoid that.
> 
> But the v2.03 branch already returns TARGET_WAITKIND_STOPPED.  And that 
> causes GDB to report SIGTRAP on every breakpoint instead of recognizing 
> the breakpoint as such.
> 

I got SIGTRAP only on hardware breakpoints (eg. hbreak).

break, tbreak seems to work Ok.

Andris