If you compile your code with -g (debugging support), and "just run" normally, it should crash and create a core file in the working dir. (do a ls -la to find it)
If you gdb --core=<your core file here> it will point you to the offending instruction (helps if you are running on the dir where you have your source code :-) otherwise you should add --directory=<your sources> paulo > Dear Mark, Dmitri, Xavier, Dave, and Tom, > thank you very much for your suggestions. > First of all, I tried the compilation > with -fbounds-check option and I did not get any error > message. > When I checked the site http://gcc.gnu.org/wiki/GFortran > our gfortran which shows: > fu...@e3sfc32:~/ngs-fdcn-code> gfortran --version > GNU Fortran (GCC) 4.4.0 20081011 (experimental) [trunk revision 141054] > Copyright (C) 2008 Free Software Foundation, Inc. > seems to be the latest now. > > There is no file to read in as this is the > very primitive code for the new algorithm test, > not the production code(=reference code). > > We are going to try to learn gdb so that > we can understand where the segfault comes from. > > I will keep you updated. > Thank you very much for your help > Best wishes, Fumie > _______________________________________________ > Beowulf mailing list, Beowulf@beowulf.org > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf > -- Paulo Afonso Lopes | Tel: +351- 21 294 8536 Departamento de Informática | 294 8300 ext.10702 Faculdade de Ciências e Tecnologia | Fax: +351- 21 294 8541 Universidade Nova de Lisboa | e-mail: p...@di.fct.unl.pt 2829-516 Caparica, PORTUGAL _______________________________________________ Beowulf mailing list, Beowulf@beowulf.org To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
