Re: new gdb/gdba code has bug with absolute source filenames

[Bruce Stephens <Bruce.Stephens@isode.com>]

Nick Roberts <nick@nick.uklinux.net> writes:

[...]

> I don't know if this is a bug in gdb or gcc or normal output. I
> don't see why gdb can't find the compilation directory from the
> executable. You used gcc version 3.3.3, is that a stable version?

No.  I get the same with Debian's gcc-3.2, which is 3.2.3 (possibly
with minor Debian patches).

>  > Perhaps I'm being naive, but it looks to me like gdb-source-info ought
>  > to be looking at "Located in ..." and just believing it.  (Possibly
>  > this wouldn't work for Windows or older gdbs or something.)
>
> It *does* use "Located in ...". Below is a patch that should work in your
> case. I'm not sure whether I should commit it to the repository though.

You're right.  I was suggesting it shouldn't be interested in the
compilation directory, but that probably *is* naive.

Your patch seems right to me, but I can understand your
uncertainty---this is probably something that shouldn't happen.

[...]