Date: Sun, 13 Jun 1999 11:38:04 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Paul Van Belinghen <pvanbell AT cloud9 DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: can't debug with djgpp
In-Reply-To: <3761AEF6.3FD81185@cloud9.net>
Message-ID: <Pine.SUN.3.91.990613113728.17906X-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 11 Jun 1999, Paul Van Belinghen wrote:

> I found that I could not debug a program with Rhide (I tried c, ada, and
> fortran sources). Even though the "-g" option is used in compilation,
> Rhide still displays the "debug info not available" message when I try
> to step or trace.

Could it be that you also have the -s switch in the options?  If so,
remove that switch.

> I found some other people who had this problem in this
> newsgroup but no one could explain it. I tried using -gstabs and -Wall
> but to no avail. Am I supposed to see a .coff file in the compilation
> directory?

No, the debugging info is put into the .exe file produced by the
compiler.  The only thing the debugger needs is the .exe file compiled
and linked with -g.

If you cannot figure this out, add -v to the compiler switches and
post here everything it prints during compilation and linking.