RE: Problem with source paths with new Cygwin release

[Kristian Otnes <kristian dot otnes at tevero dot no>]

An additional comment/warning: I also had to go back on the 'cygutils'
module from 1.2.1-2 to 1.1.4-2, since otherwise 'make' seemed to crash.
Obviously some incompatibility there.

>Does command line gdb (of the same version) suffer from the same
>problem?

I am not too familiar with GDB, but if I used the GDB console and
changed the directory to where the source file was, then I would be
able to see the source code for all source files in that directory.
In other words confirming that path info was lost somehow. Maybe
when reading symbols etc from the ELF file?

>> Is it likely that rebuilding Insight after an upgrade would also
>> solve the problem?
>
>Not sure. There's a relatively easy way to find out, though! ;-)

Heh-heh, I knew someone would say that... I will see if I get around to
it...

Kristian


>===== Original Message From Keith Seitz <keiths@redhat.com> =====
>On Thu, 2003-09-04 at 12:57, Kristian Otnes wrote:
>> Today after updating the Cygwin environment, Insight started
>> having problems with source paths when doing high level debugging.
>> Most source files are shown only in assembly code, and when
>> using the Insight function browser, the source paths seem to have
>> been stripped away from almost all source files. Thus, only
>> assembly code is shown.
>
>Does command line gdb (of the same version) suffer from the same
>problem?
>
>> Anyone happen to know the reason?
>
>Not off hand, sorry.
>
>> Is it likely that rebuilding Insight after an upgrade would also
>> solve the problem?
>
>Not sure. There's a relatively easy way to find out, though! ;-)
>
>Keiht

Kristian Otnes (kristian.otnes@tevero.no)
Tevero AS (www.tevero.no)
P.O.Box 96
NO-1317 Baerums Verk
Norway
Phone: +47 67 56 29 95