[prog] Fortran portability on linux

Kathryn Hogg kjh at flyballdogs.com
Mon Jun 7 22:31:42 EST 2004


Shirrell said:
> Unfortunately the module runs fine here and I have only the information
> from the
> customer.  The following is a report on what happens:
>
>    Abort
>   "according to the trace, it is receiving (and handling) a SIGABRT
> signal"
>
>   these results are seen on a Red Hat 7.1 system running
>    Kernel: 2.4.20aa1
>    Glibc: 2.2.4-33   The same results were senn on Red Hat Advanced
> Server 2.1 running
>    Kernel 2.4.9-e.38smp
>    Glibc 2.2.4-32.11

You can get SIGABRT for the following reasons:

1. kill -ABRT <pid>
2. call abort()
3. call raise(SIGABRT)
4. an assertion failed

obviously more of a stack trace and any output from the program would be
helpful.

-- 
Kathryn
http://womensfooty.com


More information about the Programming mailing list