------- Comment #7 from fxcoudert at gcc dot gnu dot org 2007-07-13 15:47
-------
(In reply to comment #6)
> Bugs where the compiler proper crashes when run under the driver, but not when
> run directly, can often be reproduced by varying the amount of space taken up
> by environment variables, e.g.
Excellent advice, thanks very much!
By making a variable x that contains 1064449 successive "1" characters, I get
the following:
$ X=$x c:/msys/1.0.10/home/fx/irun/mingw/libexec/gcc/i386-pc-mingw32/4.3.0/f951
.exe a.f90 -quiet
Segmentation fault
Unfortunately, I can't really debug it, because gdb itself segfaults when used
with such a large environment variable. In fact, most programs I tried do
segfault when used with this large environment variable (including as, ld,
flex).
So... now the question is more about how the driver ends up creating so large
environment variables.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2007-04-13 15:20:21 |2007-07-13 15:47:18
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31519
