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

[Bruce Stephens]

Andreas Schwab <address@hidden> writes:

> Bruce Stephens <address@hidden> writes:
>
>> Actually, it did seem to fix the problem for the test example.  But
>> didn't seem to for a real program with a much longer file name.
>
> Can you step through gdb-frame-handler with edebug and look at gdb's
> output in gdb-partial-output-buffer?

I don't need to.  The problem is right at the beginning.  As Nick
pointed out, for the broken case, gdb doesn't report the compilation
directory, so the first test fails, and gdb-view-source is set to nil.

> I tried it with real long filenames and function names, and it
> didn't fail for me.

I no longer think that it's length.  I think it's that absolute and
relative filenames end up different, for some reason.  I guess this is
the kind of thing that may well vary depending on debugging format,
compiler, and platform.

[...]