Date:	Mon, 24 May 1999 16:17:51 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	pavenis AT lanet DOT lv
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: gdb 4.18 for DJGPP (alpha)
In-Reply-To:	<B0000087946@stargate.astr.lu.lv>
Message-ID:	<Pine.SUN.3.91.990524161540.7396E-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

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.

- Raw text -