Mail Archives: djgpp/1998/09/02/18:15:27
Eli Zaretskii 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.
>
> 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).
I do have 2.8.1, and I tried -gstabs, but it took a level which I didn't
understand or feel like looking up, so I tried with 0,1, and then with 2
"-gstabs2" it worked! It also works with "-gstabs+". Great. I'll change all
of my projects (and the default project) to use that debug info. While were
on this topic, if "-gstabs+" is so much better, than why isn't it used by
default by RHIDE?
--
(\/) Endlisnis (\/)
s257m AT unb DOT ca
Endlisnis AT GeoCities DOT com
Endlis AT nbnet DOT nb DOT ca
- Raw text -