Re: Add fullname to breakpoint output

[Nick Roberts <nick@nick.uklinux.net>]

> > Hi,

> > I wrote a patch that adds the fullname to breakpoint output.

> > (gdb) -break-insert main
> > ^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
> > addr="0x080483c3",func="main",fullname="/home/bob/cvs/src/gdb/test.c",
> > file="test.c",line="8",times="0"}
> > (gdb)

> > I would like confirmation on this before I go through the effort to
> > fix the testsuite.

The CLI output doesn't give the absolute pathname:

(gdb) break main
Breakpoint 1 at 0x804856c: file mytest.c, line 36.

so doesn't this add to the inconsistency? Since, as has been said before, on
stopping CLI gives the absolute pathname:

(gdb) run
Starting program: /home/nick/mytest 

Breakpoint 1, main (argc=1, argv=0xbffff7d4) at mytest.c:36
^Z^Z/home/nick/mytest.c:36:466:beg:0x804856c
(gdb) 

while MI gives the relative pathname:

-exec-run
^running
(gdb) 
*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x0804856c",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff7d4"}],file="mytest.c",line="36"}

I don't think any of this would matter much if the search path for source
files could be accessed by the front-end. Currently, however, unlike `path',
`dir' resets rather than lists the current setting and the front-end can't
(easily) access $cdir.

Would it be a good idea to make the source path, $cdir, $cwd read-only 
convenience variables?

Nick