X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	"Michael Lazarev" <milaz AT newmail DOT ru>
Newsgroups:	comp.os.msdos.djgpp
References:	<3c5ebc9b AT MAIL DOT mhogaming DOT com> <a3n8cv$jpv$1 AT newsg1 DOT svr DOT pol DOT co DOT uk>
Subject:	Maybe it's all GCC's blame
Date:	Tue, 5 Feb 2002 12:07:02 +0300
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-Original-NNTP-Posting-Host:	213.59.208.71
Message-ID:	<3c5fa244@MAIL.mhogaming.com>
X-Original-Trace:	5 Feb 2002 02:13:40 -0700, 213.59.208.71
X-COMPLAINTS:	Report abuse to abuse AT mhogaming DOT com
Lines:	74
Organization:	Newshosting.com - Highest quality at a great price! www.newshosting.com
NNTP-Posting-Date:	05 Feb 2002 09:08:23 GMT
NNTP-Posting-Host:	f8876a80.news.newshosting.com
X-Trace:	DXC=[;CM]9>;3Egla?:O2D6CffX`1N4>^k1LciF6BbIV4YYbnEaR^cOTQ`dBVh7\ik=c`cm2lengNZCfeBOWBh AT 4SCJe\44h=O^TVnf
X-Complaints-To:	abuse AT newshosting DOT com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Matthew Smith wrote:

> > of a class member functions, but it is impossible to set a breakpoint in
.h file.
>
> You should not have executable code in a .h file, so breakpoints there
> are unnecessary

Yes, you are right. Header files are for declarative purposes.
Maybe Java programming made me forget it. I wonder how I ever didn't write
all functions' bodies inside of the class :)

After having split code of passwords.h into passwords.h with class
declaration only and passwords.cpp with realisation of the class, I moved to
project mode, which is only problematic for me.

Things go even worse, because after "Build all" some time RHIDE warns me
that I cannot use breakpoint in some line; some time it warns me only after
CTRL+F9, and it is dreadful. It lets me only one choice "OK", when I wold
prefer not to run a program at all, if breakpiont is not set.

I think the last thing described here is RHIDE bug, not compiler's one,
because RHIDE must have debugging information on all lines of already built
program, and must warn that it is unable to set breakpoint right after
attempt of setting it.

> > 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.
> >
>
> Try ctl-F2 (program reset) before rebuilding

I am sorry to say, it didn't help. I am even more sorry to say that it
seemed funny to me, but anyway, I gave it a try.

To reproduce this problem, use a multi-moduled project. After rebuilding,
starting by F8, tracing, successful finish with code 0, and another attempt
of starting with F8, program executes completely without stop. Breakpoints
in _main_ module work just fine, and I found "detour" solution. Set a
breakpoint on the first function call or assignment line in main module.
Then F8 will work fine always.

This solution is much more funny, but it works :)

> > In another randomly reproductable case RHIDE crashes.
> > Some times it is Build all, or Open project commands.
>
> Yes, I find a few instabilities with RHIDE 1.4.9 too.
>
> > I don't use any -O and any other optimizations.
> > Can anybody tell me what happens and is there any solution of my
> problem?
> >
>
> Not until gcc is fixed to produce the right line numbers.  Ideally
> RHIDE/gdb could be
> adjusted to step to lines with no generated code too, by taking the
> next line which does have code.  It seems bizarre that you can't have
> a breakpoint on the line which defines a function.

I am agree with you. I tried gdb, and saw that gcc really produces wrong
line numbers and even wrong function lists. Names of class member functions
are corrupted, and there is wrong debugging info for them.

Now I understand why RHIDE developers don't waste their time for working on
debugging features.

Anyway, thank you.

- Raw text -