--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-06-18
20:17 ---
Yes it is (same backtrace and all). Well, PR15966 was GCC's most reported bug,
but this was an ex aequo. Now, it's be a not-for-share gold medal.
*** This bug has been marked as a duplicate of 15966 ***
--- Additional Comments From reichelt at gcc dot gnu dot org 2005-06-07
23:46 ---
This seems to be a duplicate of our famous bug PR 15966.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21902
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-05
06:48 ---
Note I started to reduce this and removed a whole function or two and was able
to reduce further but I
stoped because I ran out of time.
--
What|Removed |Added
--- Additional Comments From schnetter at aei dot mpg dot de 2005-06-05
18:07 ---
Created an attachment (id=9034)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9034action=view)
Failing source code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21902
--- Additional Comments From schnetter at aei dot mpg dot de 2005-06-05
19:29 ---
This segmentation fault seems to be caused by the combination of the
declaration
character :: msg(100)
and the statement
write (msg, '(Error in call to GESV, info=,i2)') info
--- Additional Comments From schnetter at aei dot mpg dot de 2005-06-04
23:15 ---
I tried to reduce the failing source code, but failed to achieve much.
Depending on what lines I remove, the error changes, sometimes turning into a
bare segmentation fault. Even renaming the source
--- Additional Comments From schnetter at aei dot mpg dot de 2005-06-03
18:25 ---
Created an attachment (id=9022)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9022action=view)
Failing gzipped source code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21902
