Date:	Mon, 20 May 1996 11:38:39 +0200 (METDST)
From:	Robert Hoehne <robert DOT hoehne AT Mathematik DOT TU-Chemnitz DOT DE>
To:	Broeker AT physik DOT rwth-aachen DOT de
Cc:	djgpp-workers AT delorie DOT com, Broeker AT axpmgr DOT physik DOT rwth-aachen DOT de
Subject:	Re: gdb problem with foo.cpp, with a fix
In-Reply-To:	<01I4TFXFDRSI00167C@mail.rwth-aachen.de>
Message-Id:	<Pine.HPP.3.91.960520112939.9938A-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version:	1.0

On Fri, 17 May 1996 Broeker AT physik DOT rwth-aachen DOT de wrote:

> Hello, everyone
> 
> The problem manifests itself this way: for 'gcc -g foo.cpp', all the
> DJGPP debuggers will think the source file name is 'foo.cc' instead,
> and therefore fail to find it. Eli's hint in the FAQ is only nearly
> correct, I think: he points in the direction of the "-dumpbase foo.cc"
> switch that gcc.exe will pass to cc1plus.exe in this situation, which is
> obviously not what you'd expect it to be. But this, IMHO isn't the real
> error. The 'dumpbase' information passed is completely correct in
> itself, but it is *used* in one incorrect way.
> 
I think, Eli's statement in the FAQ is correct. You bugfix solves the problem
only for some few machines or systems. I mad also a bugfix some weeks
ago and posted it to bug-gcc AT prep DOT ai DOT mit DOT edu. This bugfix has the idea,
to add a new spec modifyer to calculate the correct dumpbase name for
calling the compilers from the gcc driver.

I think changes at the gcc driver is the right place for fixing this
bug. If someone is interested in my fix, I can post it.

Robert

*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
* e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
* WWW:     http://www.tu-chemnitz.de/~rho                       *
*****************************************************************

- Raw text -