Thanks Al. That gives:
execve("./sixsV1.1", ["./sixsV1.1"], [/* 21 vars */] <unfinished ...>
+++ killed by SIGKILL +++
Killed
So it is obviously being SIGKILLed by someone/something. I don't understand the
first line of output - does that tell us anything interesting? It's really
strange - I've never had this problem before with this program, and I've run it
on many machines.
I've checked it isn't the Fortran compiler producing executables that always
die: a Hello World program compiled with the same compiler runs fine.
Is it always the case the the Out of Memory Killer will log that it has killed
something? I find the fact that I can't find anything in the logs anywhere very
suspicious.
Cheers,
Robin
On 16 Jan 2014, at 20:15, Alan Pope <[email protected]> wrote:
> On 16 January 2014 19:30, Robin Wilson <[email protected]> wrote:
>> robintw@test:~/Py6S/6S/6SV1.1$ ./sixsV1.1
>> Killed
>>
>> Does anyone have any idea what I can do to try and work out what's happening?
>>
>
> strace it?
>
> strace ./sixsV1.1
>
> Cheers,
> Al.
>
> --
> Please post to: [email protected]
> Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> LUG URL: http://www.hantslug.org.uk
> --------------------------------------------------------------
--
Please post to: [email protected]
Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL: http://www.hantslug.org.uk
--------------------------------------------------------------
