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

[Bruce Stephens]

Nick Roberts <address@hidden> writes:

[...]

> A good way to look at this output is to select
> gdb-partial-output-buffer and type undo. That way you can cycle back
> through its history. In the past I have found that edebug plays
> havoc with real time aspects of the process filter.

That's useful to know.  In this case, though, I don't see that it
would help: I can see the differing behaviour using gdb in a terminal.
gdb isn't showing the compilation directory in this case, whereas with
a relative filename ("gcc-3.2 -g3 -o hello ./hello.c") it does.  I'd
guess details of how gdb-partial-output-buffer evolves probably
doesn't matter.

I don't know which program is at fault.

bruce% gcc-3.2 -g3 -o hello /tmp/hello.c
bruce% gdb hello
GNU gdb 6.0-debian
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...
(gdb) break main
Breakpoint 1 at 0x8048340: file /tmp/hello.c, line 4.
(gdb) run
Starting program: /tmp/hello
 
Breakpoint 1, main () at /tmp/hello.c:4
4       exit(0);
(gdb) info source
Current source file is /tmp/hello.c
Located in /tmp/hello.c
Contains 6 lines.
Source language is c.
Compiled with DWARF 2 debugging format.
Includes preprocessor macro info.