Date: Tue, 5 May 1998 19:44:38 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: C++ debugging with GDB
In-Reply-To: <Pine.SUN.3.91.980505161123.28653D-100000@is>
Message-ID: <Pine.A32.3.91.980505193617.62812A-100000@ieva06.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk



On Tue, 5 May 1998, Eli Zaretskii wrote:

> 
> On Tue, 5 May 1998, 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
> 
> Did you use patched libraries?  Robert used several patches to library 
> functions inside src/debug, which he posted to djgpp-workers.  You need 
> to use them.  (I'm not sure these problems are because of those patches.)

There were more than one attempt:
  - there was note in readme in gdb416s.zip to patch one of the files in 
    src/debug. Tried but got the result described above. There is also 
    the patched version inside sources of RHIDE: also there were no 
    results
  - I tried to use libc.a from alpha djlsr202 (rebuilt it from sources, 
    which was not very easy with gcc-2.8.0, I didn't have 2.8.1 at that 
    time) but still got the same. 

In RHIDE I found that after Ctrl-C the program I'm being debugged no more
exist. The main idea for building gdb-4.16 from sources was to use it
(libgdb.a) in RHIDE. Unfortunatelly I didn't succeed to get expected 
reaction to SIGINT.

Andris