Mail Archives: djgpp/2002/12/06/13:15:09
Never mind. I found a previous post (copied below) that answered my
question. Guess I didn't search hard enough the first time. You have
to use the switch -gcoff.
From: Eli Zaretskii (eliz AT is DOT elta DOT co DOT il)
Subject: Re: debbuging with rhide. NOT. :(
Newsgroups: comp.os.msdos.djgpp
Date: 2002-11-24 02:25:07 PST
On Sun, 24 Nov 2002, Ekskavaator wrote:
> "The selected breakpoint is invalid, probably this file
> is not compiled with debugging information or for this
> line is no code generated.
> (Breakpoint at line 14 in file answer.cpp)"
>
> Such error if i try to put a breakpoint.
Try compiling with -gcoff instead of a mere -g.
Alternatively, get a newer version of RHIDE (or an older version of
GCC).
The problem is likely to be that the latest GCC produces DWARF2 debug
info when you compile with -g, but the version of RHIDE you have
doesn't
know about the DWARF2 format.
riumsemaj AT hotmail DOT com (James Muir) wrote in message news:<a689d86c DOT 0212051940 DOT 4e8cf581 AT posting DOT google DOT com>...
> Hi,
>
> I just installed RHIDE 1.4.9 last week (on Windows98) and I have a
> problem that I can't seem to solve from the documentation.
>
> I can't seem to get the debugging functions to work from inside RHIDE.
> For example, when I compile a simple C++ program, say test.cpp, RHIDE
> says:
>
> executing:
> gcc -IC:/djgpp/include -g -c test.cpp -o test.o
>
> Now, when I try "Step Over" the code, RHIDE says:
>
> This program has no usable debugging information. Try
> to compile it with the -g switch.
>
> but, it seems the -g switch was already used. I've tried adding other
> debugging switches from inside RHIDE but I still get the same error.
> RHIDE also quickly flashes this message when I try to debug:
>
> gcc -o test.exe test.o -lstdcxx -lm
>
> but I think this is just a linking step. Any idea what's wrong? I'd
> like to just be able to hit F8 when I want to step into my code.
>
> Thanks.
>
> -James
- Raw text -