> On Jul 12, 2018, at 11:02 AM, Jeff Squyres (jsquyres) <[email protected]>
> wrote:
>
> On Jul 12, 2018, at 10:59 AM, Noam Bernstein <[email protected]>
> wrote:
>>
>>> Do you get core files?
>>>
>>> Loading up the core file in a debugger might give us more information.
>>
>> No, I don’t, despite setting "ulimit -c unlimited”. I’m not sure what’s
>> going on with that (or the lack of line info in the stack trace). Could be
>> an intel compiler issue?
>
> If you're running your job through a job scheduler (such as SLURM or Torque),
> you may need to set something in the config and/or environment of the job
> scheduler daemons to allow launched jobs to get core files.
>
> E.g., if you "ulimit -c" in your interactive shell and see "unlimited", but
> if you "ulimit -c" in a launched job and see "0", then the job scheduler is
> doing that to your environment somewhere.
I am using a scheduler (torque), but as I also told Åke off list in our
side-discussion about VASP, I’m already doing that. I mpirun a script which
does a few things like ulimit -c and ulimit -s, and then runs the actual
executable with $* arguments.
I’m trying to recompile with gcc/gfortran to see if that changes anything.
Noam
_______________________________________________
users mailing list
[email protected]
https://lists.open-mpi.org/mailman/listinfo/users
