From: pavenis AT lanet DOT lv
To: Mel Corley <mcorley AT engr DOT latech DOT edu>, rhide AT listbot DOT com
Date: Mon, 26 Mar 2001 11:36:31 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: gcc2953 and RHIDE debugging
Cc: djgpp-workers AT delorie DOT com
Message-ID: <3ABF29BF.8067.F04DC@localhost>
In-reply-to: <3ABD620B.2030203@engr.latech.edu>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 24 Mar 2001, at 21:12, Mel Corley wrote:

> I upgraded to gcc2953 in Windows 98 and now none of the debugging 
> features work in RHIDE, e.g., F7 & F8 keys for stepping through code. 
> Not even breakpoints work. There must be a new compiler option that 
> needs to be set in the RHIDE options? Or should I just go back to gcc2952?

Shortly:  try -gstabs instead of -g

Seems that I have missed one breakage:
	-gcoff (same as -g for DJGPP) seems to be broken in gcc-2.95.3 as
	  it often (but not always) puts 0 as line number in debug info 
	  instead of real line number

Currently one can use -gstabs or -gstabs+ instead of -g with gcc-
2.95.3. 

I was not able to test any other systems (different from DJGPP) as 
under Linux gcc doesn't support -gcoff. Perhaps one could check and 
report results here.

I have seen similar behaviour earlier in some cases (eg. gcc/libgcc2.c in
gcc sources) with gcc-2.95.2, but it was not critical that time.

I could rebuild gcc-2.95.3 to enable -gstabs by default, but in this case
we'll break symify and ability of fsdb and edebug32 to see debug info

For comparisson: my build of gcc-3.0 20010314 development version 
(from CVS) for DJGPP seems to have correct line numbers in debug 
info with -gcoff.

Andris