Date:	Wed, 6 May 1998 09:55:59 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: C++ debugging with GDB
In-Reply-To:	<354F8FBB.B6B4C5CA@gmx.net>
Message-ID:	<Pine.A32.3.91.980506094956.50318A-100000@ieva06.lanet.lv>
MIME-Version:	1.0

On Tue, 5 May 1998, Robert Hoehne wrote:

> Andris Pavenis wrote :
> > 
> >    - Previously I was not able to get normal reaction to SIGINT in DJGPP port of
> >      gdb-4.16 when I built it from sources (The process I'm debugging does no
> >      more exist when I'm getting next gdb prompt after SIGINT, this is not so
> >      in binary archive built by Robert [gdb416b.zip] and in binaries I have built
> >      under Linux
> 
> I don't remember exactly about the gdb416b.zip archive, but I know, that
> there
> were some problems so I disabled it later completely by killing the
> debugged process if y signal occours. After some analizing and thinking
> and
> not finding a solution I came to the fact, that it is currently
> _impossible_
> to catch any signals when debugging on DJGPP without doing many changes.
> 

Maybe. But looks that binaries from gdb416b.zip behaves as I expect:

  the program is not killed after SIGINT (which is the same behaviour I'm
  getting in Linux with gdb-4.16 and gdb-4.17 I built from sources). 
  With binaries from gdb416b.zip I'm able to interrupt program with
  Ctrl-C and continue debugging. I didn't met serious problems with
  these binaries

Andris

- Raw text -