Date: Wed, 2 Sep 1998 14:22:51 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Endlisnis <s257m AT unb DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: RHIDE Can't debug this. Was: Am I retarded -or- Why is my exe size so big?!?
In-Reply-To: <35EC63E9.4FD54CF0@unb.ca>
Message-ID: <Pine.SUN.3.91.980902141653.2989A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 1 Sep 1998, Endlisnis wrote:

> You can step through the code, but setting a break-point (by
> pressing F4) on line #132 (or #133) in the main file will cause the entire
> program to be executed, not stopping where I desired.

I can confirm this problem.  I ran this under GDB (I don't use RHIDE), 
and it seems that the problem is in the debug info generated by the
compiler: when I set a breakpoint on one of these lines, the address of 
the breakpoint GDB prints is *outside* `main' (I can see all the 
addresses of instructions in `main' by typing "disassemble main" at the 
GDB prompt).

So I would tend to think that the C++ compiler has some bug in the COFF 
debug info it produces in this case.  If you have GCC 2.8.1 installed, 
you might try compiling with -gstabs instead of -g and see if that helps 
(this will force the compiler to produce debug info in the STABS format, 
which has less limitations and misfeatures than COFF).