Date:	Thu, 2 Mar 2000 11:50:27 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	leon <Leon AT caresystems DOT com DOT au>
cc:	djgpp AT Delorie DOT com
Subject:	Re: possible bug in DJGPP gdb build
In-Reply-To:	<38BDD2A7.7DD8B76A@caresystems.com.au>
Message-ID:	<Pine.SUN.3.91.1000302114817.25214B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 2 Mar 2000, leon wrote:

> the problem to be described was not replicated and behaved ok on mingw32
> and cygwin (i have asked those users to test it for me - all came back
> ok)
> 
> but it is evident in djgpp!

Please use the same Subject line when you post follow-ups.  Otherwise, it 
is very hard to track the thread.

See my reply to your other message (this is a FAQ).  Mingw and Cygwin use 
a different binary format, so the basic deficiencies of the COFF debug 
info don't show there.

- Raw text -