Re: [patch 4/9] TUI: Use internally fullname

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 22 Jan 2013 09:46:48 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: tromey@redhat.com, gdb-patches@sourceware.org
> 
> On Tue, 22 Jan 2013 09:24:59 +0100, Eli Zaretskii wrote:
> > > But for NAME - the string which user entered in "break ./gdb.base/return.c:main"
> > > - has no compilation nor "current" directory.
> > 
> > What is the semantics of such a 'break' command?  Does "." here mean
> > the current directory?  Or does it mean something else?
> 
> It is compilation directory (DW_AT_comp_dir) relative name (therefore CU's
> DW_AT_name).

But then it means that directory is somewhere we could get at it,
right?  And yet you said "has no compilation directory".  What am I
missing?

> Moreover recent GDBs allow to use also any trailing part, therefore not just
> "break ./gdb.base/return.c:main" and "break return.c:main"
> but also "break gdb.base/return.c".

It sounds strange to me to use "." to mean anything but GDB's current
directory, but if that's a long living tradition, so be it.

> > > So I do not understand why MS-Windows stat call does not provide st_ino from
> > > those fields.
> > 
> > Because MS didn't bother to code that.
> 
> BTW Free wine32 also has st_ino == 0; I understand it needs to be compatible.
> Free wine64 (with 64-bit PE32+ executable) also behaves the same.

Compatibility is a virulent disease.