Mail Archives: djgpp-workers/2001/01/06/17:07:31
> If you are talking about changes added a few months ago, they are
> mine, I think.
In that case: hey, you missed a spot ;-)
> Where did you look? in the "gcc -S" output? That's not where I
> looked.
I checked both the assembly and the object file.
The result of the .file directive was intact in both cases.
Besides this, the stabs-based files also contained a few more
references to files and headers; they too were intact in the
object files.
> Here's how to reproduce this:
> [snip]
> Breakpoint 1, main (argc=1, argv=0xfff334a0) at c:\dir1\dir2\d:5
> 5 c:\dir1\dir2\d: No such file or directory (ENOENT)
Hmm - then the 14-char thing may be a gdb limit, unrelated to
binutils. It may even be specific to the DJGPP port of gdb/binutils.
I get the results below (and as you can see, I'm using web2c to
refine configure's support for configuring subdirs; there was indeed
some breakage there). Do note that neither gcc, binutils nor gdb are
standard DJGPP versions; in each case I built my own (though usually
based on diffs that came with DJGPP packages of earlier versions).
The file foo.c simply contained a do-nothing main() returning 0.
H:\Tmp\Source\web2c-7.3.3\texk\web2c\web2c>gcc -gcoff h:\Tmp\Source\web2c-7.3.3\texk\web2c\web2c\foo.c
H:\Tmp\Source\web2c-7.3.3\texk\web2c\web2c>gdb a.out
GNU gdb 5.0
Copyright 2000 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-pc-msdosdjgpp"...
Reading symbols from H:/Tmp/Source/web2c-7.3.3/texk/web2c/web2c/a.out...done.
[GDB] br main
Breakpoint 1 at 0x1d73: file h:\Tmp\Source\web2c-7.3.3\texk\web2c\web2c\foo.c, l
ine 4.
[GDB] r
Breakpoint 1, main () at h:\Tmp\Source\web2c-7.3.3\texk\web2c\web2c\foo.c:4
4 return 0;
[GDB] q
- Raw text -