X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: Andrew Cottrell <andnews AT ihug DOT com DOT oz DOT au>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Debugging in RHIDE (1.4.9)
Date: Tue, 05 Feb 2002 21:22:57 +1100
Organization: ihug (Sydney)
Lines: 40
Message-ID: <c0cv5ugtvvadl3aoect3rd5oj3m7epf93d@4ax.com>
References: <3c5ebc9b AT MAIL DOT mhogaming DOT com>
NNTP-Posting-Host: bugstomper.ihug.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: lust.ihug.co.nz 1012904535 7860 203.109.250.24 (5 Feb 2002 10:22:15 GMT)
X-Complaints-To: abuse AT ihug DOT co DOT nz
NNTP-Posting-Date: Tue, 5 Feb 2002 10:22:15 +0000 (UTC)
X-Newsreader: Forte Agent 1.9/32.560
Cache-Post-Path: bugstomper.ihug.com.au!unknown AT p592-apx1 DOT syd DOT ihug DOT com DOT au
X-Cache: nntpcache 2.3.3 (see http://www.nntpcache.org/)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>Hi all. I am seeking for help in debugging C++ programs in RHIDE 1.4.9.
SNIP....
>To be more exact, breakpoint is set, there is no warning that this line has
>no debugging info, but program never stops on it.
>Note that this line is reachable by tracing (step-by step execution).
>
>Also, without rebuilding, randomly, after having finished program and
>pressed F8 again, even no step-by-step execution happens, program "flies
>away", gives out the result, and RHIDE reports program exit code 0.
>
>In another randomly reproductable case RHIDE crashes. Some times it is Build
>all, or Open project commands.
>
>I use the following environment:
>    bnu2112, djdev203, gcc303, gpp303, mak3791, rhid149, txi40
>on Win 4.10.1998, at PII 233 with 288Mb RAM.
>
>I don't use any -O and any other optimizations.
>Can anybody tell me what happens and is there any solution of my problem?

It sounds like you have hit multiple issues in the one session. I hope
the following helps:-
1)  There are known problems with GCC 3.x.x and GDB 5.x.x with C++.
Some of the issues you have seen may be because of this.  A workarund
is to try the old fashioned printf() debugging or in the case of C++
cout <<. Another way is to go back to GCC 2.9.5.3.
2)  Trey startting Rhide with a "-S" option and see if this helps, if
it does then you may have a buggy bios.
3) You could try Andris's Rhide 1.4.9.1 available from
http://home.lanet.lv/~pavenis/rhide.html and let me know if this helps
with the crashes.

If you go back to GCC 2.9.5.3 and use Rhide 1.4.9.1 and the crashes
still occur could you let me know.

Hope this helps.
Andrew