Message-Id: <199803201514.RAA66266@ieva06.lanet.lv>
From: "Andris Pavenis" <pavenis AT laima DOT acad DOT latnet DOT lv>
To: djgpp AT delorie DOT com
Date: Fri, 20 Mar 1998 17:12:07 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Debug and "/" with RHIDE / WIN95 / DJGPP
In-reply-to: <m0yG1E6-000S2uC@inti.gov.ar>
References: <35121bc2 DOT 5278501 AT news DOT on-luebeck DOT de>
Precedence: bulk


> DarkSoft AT GMX DOT Net (^Hawk^ (Thorsten Kaben)) wrote:
> 
> > If I try to run the exe in step mode within the RHIDE then the IDE
> > tould me that there are none usefull debug informations and I should
> > use the "-g" switch. But it don't cares whether I've the "-g" as
> > compiler option or not ... this message comes in spite of it ... of
> > course if I've recompiled the source ... with the external debugger of
> > the RHIDE it works fine. Why not within the RHIDE ? At this moment I
> > can't follow the source because of this. :((=
> 
> I have no idea about that, it works 100% ok in the 4 machines I have with 
> RHIDE.
>  

I can imagine such effect when somebody is building rhide himself.
Compiling gdb sources under DOS is tricky and if somebody tries
to get it compiled by force (and does not have all neaded tools installed)
he can get not working libgdb.a.

At begin I once got such and the result were very similar to the 
described above even if executable had debug information. 

Therefore my suggestion for such situation are following:
   - at first to use precompiled binary of RHIDE (if there were an attempt
     to build RHIDE before);
   - after that one can try to debug program with gdb.exe:

Andris Pavenis