RE: Problem with source paths with new Cygwin release

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

It must be a GDB/Cygwin related problem as you suggest. I am using
a cross target compiler for PowerPC/ELF.

Maybe related to somehow Cygwin handles paths? I see the paths in the
ELF file. Might be an API change somewhere?!

Since Insight includes GDB when compiling, I am not sure how closely
the Insight snapshots follow GDB updates. And I don't know how closely
GDB follows Cygwin or vice versa. In other words, it can be a number of
causes.

The best thing is probably to build a clean new version and see if
the problem persists. It could maybe be fixed if the build uses some
libraries included with cygwin/cygutils modules, but I have no idea
how that works.

I will see, as I mentioned, if I can try to rebuild things at some
point.

Thanks for your help so far Keith.

Kristian

-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com] 
Sent: 4. september 2003 23:31
To: Kristian Otnes
Cc: insight
Subject: RE: Problem with source paths with new Cygwin release

On Thu, 2003-09-04 at 14:11, Kristian Otnes wrote:

> This would typically give a GDB printout:
> 
> 879	foo.c: No such file or directory.
> 	in foo.c
> 
> whereas it shows a few lines of C code if I use the older
> cygwin/cygutils modules

If command line gdb is giving you this error, it looks like gdb's symbol
readers might be screwed up.

Can you clarify: You're debugging native cygwin apps with gdb/Insight or
a cross targetting ppc-elf?

Keith