This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [Fortran] Lapack test suite results for i686-pc-linux-gnu


Peter Schmid wrote:

> Debugging xlintimd compiled by gcc-3.0
> (gdb) set args < dtime.in > dtime.out 2>&1
> (gdb) r
> Starting program: /mnt/LAPACK/TIMING/xlintimd < dtime.in > dtime.out 2>&1
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x080db2f6 in f_setarg (argc=1, argv=0xbffff83c) at setarg.c:27
> (gdb) bt
> #0  0x080db2f6 in f_setarg (argc=1, argv=0xbffff83c) at setarg.c:27
> #1  0x080db1e3 in main (argc=1, argv=0xbffff83c) at main.c:55
> #2  0x40057baf in ?? ()
> (gdb) l
> 22      f_setarg(argc, argv) int argc; char **argv;
> 23      #else
> 24      f_setarg(int argc, char **argv)
> 25      #endif
> 26      {
> 27      f__xargc = argc;
> 28      f__xargv = argv;
> 29      }

This one is known - sadly I do not know what to do about it.  The timing
programs in the LAPACK distribution contain large arrays (that are only
used "sparingly").  Unfortunately, after allocating all static memory in
a program, the linking in of the libf2c library causes these static
variables (f__xargc and f__xargv) to be allocated at high addresses.  If
your RAM+SWAP isn't larger than this address, you'll get a SIGSEGV.

Hope this helps,

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]