Date: Tue, 5 May 1998 16:16:01 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: Nate Eldredge <nate AT cartsys DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: C++ debugging with GDB
In-Reply-To: <B0000029294@stargate.astr.lu.lv>
Message-ID: <Pine.SUN.3.91.980505161123.28653D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


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.)

Also, you shouldn't draw any conclusions from what GDB does on Linux.  
Linux uses ELF, so much of its debugging support is totally different.

> One suggestion. I think we should get rid of these batch files. I think
> that the way that is used in ports of gcc-2.8.0 and gcc-2.8.1 is better:

Sure, I agree completely.  I only mentioned those batch files as a means 
to understand what needs to be done and which files are required for the 
DJGPP build.  I didn't mean to say Andrew should use those batch files in 
building 4.17.