Re: [RFC] fullname attribute for GDB/MI stack frames

[Bob Rossi <bob@brasko.net>]

On Wed, May 04, 2005 at 07:40:35PM -0400, Christopher Faylor wrote:
> On Wed, May 04, 2005 at 05:07:17PM -0400, Daniel Jacobowitz wrote:
> >If it's going to open files, it _does_ matter.  You said that the
> >current directory (and presumably the current drive) are global on this
> >platform.  But the current directory is not stable across time.  If the
> >front end changes the current directory after talking to GDB, suddenly
> >it won't be able to open files.
> 
> Right.  Presumably, on windows 9x you could do something like:
> 
> (gdb) shell
> d:
> cd \foo
> exit
> 
> and end up  invalidating anything which was previously pointing to
> d:foo.
> 
> Although, hmm.  That assumes that all of the filenames had been
> previously resolved of course.  I don't think that's necessarily true in
> gdb is it?  Wouldn't some filenames be canonicalized only as needed?

This may or may not be what you mean. However, if you do
-file-list-exec-source-files, GDB prints the filename and fullname for
every file that it knows about. The purpose of this is to let the front
end know about each and every file that GDB knows about. As I've stated
before, I believe most if not all FE's depend on the fullname to be a
unique key.

Bob Rossi