This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: g77 problems
- To: Nichols Romero <naromero at modi4 dot ncsa dot uiuc dot edu>
- Subject: Re: g77 problems
- From: Martin Malm <martin dot malm at fast dot no>
- Date: Wed, 18 Oct 2000 08:00:39 +0200
- CC: gcc-help at gcc dot gnu dot org
- Organization: FAST
- References: <200010180535.AAA2101050@modi4.ncsa.uiuc.edu>
Nichols Romero wrote:
> I ran gdb on the core dump file and this is what I got
>
> Reading symbols from /lib/libc.so.6...done.
> Reading symbols from /lib/ld-linux.so.2...done.
> #0 f_setarg (argc=1, argv=0xbffff984) at ../../../../libf2c/libF77/setarg.c:27
> 27 ../../../../libf2c/libF77/setarg.c: No such file or directory.
>
Your program core dump in the setarg.c file that is part of the libf2c.
> Where can I get setarg.c from? What package is that from?
In/around the place you found the libf2c rpm look for a file called something like
libf2c-?.src.rpm probably in a SRPMS directory. I don't know if this is part of
the rpms that come with the RH6.2 CD's but if it is look in the SRPMS directory on
the source CD's.
If you install this (rpm -ivh libf2c-?.src.rpm) then the source end up in
/usr/src/redhat/SOURCES/
You can then unpack the sources and in gdb you can set the path to the sources so
that you see the contents of setarg.c.
In gdb you can set the path to the sources using the "directory <path to source>"
command.
However the cause of the core dump is almost certainly in your own code, you
probably pass some bogus args to a function 8)
Also see man rpm and man gdb
--
Martin Malm MAIL: ovemm@fast.no / AIM: ovemm
Fast Search & Transfer ASA Phone: +47 73 20 12 24 / +47 92 08 22 73