Prev: simple graphics for fortran on windows
Next: How to compile Mopac 7.1 using g77 or gfortran
From: Marcelo Almeida de Amorim on 25 Sep 2008 15:43
I have a program that works fine when I run it manually ,but when I
execute it using cron I get the following error:

======================================================
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line
Source
libc.so.6.1 2000000000A72F11 Unknown Unknown
Unknown
hrm 4000000000CC3C70 Unknown Unknown
Unknown
hrm 4000000000CC3580 Unknown Unknown
Unknown
hrm 4000000000CC27D0 Unknown Unknown
Unknown
hrm 4000000000D00570 Unknown Unknown
Unknown
hrm 400000000055A520 Unknown Unknown
Unknown
hrm 4000000000574740 Unknown Unknown
Unknown
hrm 4000000000225A20 Unknown Unknown
Unknown
hrm 4000000000004450 Unknown Unknown
Unknown
libc.so.6.1 20000000009BBC20 Unknown Unknown
Unknown
hrm 4000000000004280 Unknown Unknown
Unknown


I am running it on a Altix, using Suse Linux Enterprise Server 10

Hope someone can help me

Thanks
From: Craig Powers on 25 Sep 2008 15:53
Marcelo Almeida de Amorim wrote:
> I have a program that works fine when I run it manually ,but when I
> execute it using cron I get the following error:
>
> ======================================================
> forrtl: severe (174): SIGSEGV, segmentation fault occurred
> Image PC Routine Line
> Source
> libc.so.6.1 2000000000A72F11 Unknown Unknown
> Unknown
> hrm 4000000000CC3C70 Unknown Unknown
> Unknown
> hrm 4000000000CC3580 Unknown Unknown
> Unknown
> hrm 4000000000CC27D0 Unknown Unknown
> Unknown
> hrm 4000000000D00570 Unknown Unknown
> Unknown
> hrm 400000000055A520 Unknown Unknown
> Unknown
> hrm 4000000000574740 Unknown Unknown
> Unknown
> hrm 4000000000225A20 Unknown Unknown
> Unknown
> hrm 4000000000004450 Unknown Unknown
> Unknown
> libc.so.6.1 20000000009BBC20 Unknown Unknown
> Unknown
> hrm 4000000000004280 Unknown Unknown
> Unknown
>
>
> I am running it on a Altix, using Suse Linux Enterprise Server 10
>
> Hope someone can help me

Try compiling with -traceback so that you can get an actual backtrace of
the error and see where it happened. The best guess I can make is that
somewhere along the line, an attempt is made to write to something like
stdout and that isn't actually connected when something runs off of cron.
From: Bil Kleb on 1 Oct 2008 06:10
Marcelo Almeida de Amorim wrote:
> I have a program that works fine when I run it manually ,but when I
> execute it using cron I get the following error:

The difference is typically your environment variables: cron jobs are
run with a blank environment. You can simulate the blank cron environment
by using the 'env' command, e.g.,

% env - ./my_code

The 'env -' will clear all environment variables.

You can then beginning adding in environment variables to see
which are necessary to set to get your cron job to run, e.g.,

% env PATH=/my/special/compiler/path:$PATH UFMTENDIAN=big ./my_code

Regards,
--
Bil Kleb
http://fun3d.larc.nasa.gov

From: Arjen Markus on 2 Oct 2008 11:27
On 25 sep, 21:43, Marcelo Almeida de Amorim
<marcelodeamo...(a)gmail.com> wrote:
> I have a program that works fine when I run it manually ,but when I
> execute it using cron I get the following error:
>
>  ======================================================
> forrtl: severe (174): SIGSEGV, segmentation fault occurred
> Image              PC                Routine            Line
> Source
> libc.so.6.1        2000000000A72F11  Unknown               Unknown
> Unknown
> hrm                4000000000CC3C70  Unknown               Unknown
> Unknown
> hrm                4000000000CC3580  Unknown               Unknown
> Unknown
> hrm                4000000000CC27D0  Unknown               Unknown
> Unknown
> hrm                4000000000D00570  Unknown               Unknown
> Unknown
> hrm                400000000055A520  Unknown               Unknown
> Unknown
> hrm                4000000000574740  Unknown               Unknown
> Unknown
> hrm                4000000000225A20  Unknown               Unknown
> Unknown
> hrm                4000000000004450  Unknown               Unknown
> Unknown
> libc.so.6.1        20000000009BBC20  Unknown               Unknown
> Unknown
> hrm                4000000000004280  Unknown               Unknown
> Unknown
>
> I am running it on a Altix, using Suse Linux Enterprise Server 10
>
> Hope someone can help me
>
> Thanks

Environment variables may very well be the problem, as Bil suggested.
One thing I ran into today is that some compilers use the environment
variable TMP (or TEMP or ...) to determine the directory where
temporary files will be opened. So, it need not be that you use
them explicitly in your program!

Regards,

Arjen
 | 
Pages: 1
Prev: simple graphics for fortran on windows
Next: How to compile Mopac 7.1 using g77 or gfortran