Date: Mon, 16 Dec 1996 18:28:26 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Alexey Kouzmitch <alexey AT ix DOT netcom DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Tracing in RHIDE
In-Reply-To: <01bbe875$4a532040$aa49bacd@alexey.ix.netcom.com>
Message-ID: <Pine.SUN.3.91.961216182553.18715W-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 12 Dec 1996, Alexey Kouzmitch wrote:

> I don't know why, but my RHIDE doesn't trace whatsoever, just jumps around
> the file... which switches should I use to make gcc generate enough
> debugging info ???

You should use -g and NOT use -s.  If you did that and it didn't help, 
maybe you are running on Windows 3.x?  If so, use hardware breakpoints 
(hbreak and thbreak commands) and don't step or trace: DJGPP debug 
support has a known problem in Windows 3.x which prevents the regular 
breakpoints from working there (it's all in the FAQ, btw).