[mvapich-discuss] Assertion failure in mvapich 1.2rc2 (fwd)

[Karthik Gopalakrishnan]

Hello.

You can try adding "ulimit -c unlimited" to you .bashrc file. This
should enable dumping core.

Regards,
Karthik

On Tue, Sep 16, 2008 at 12:17 PM, Hari Subramoni
<subramon at cse.ohio-state.edu> wrote:
>
>
> ---------- Forwarded message ----------
> Date: Thu, 11 Sep 2008 22:00:57 +0200
> From: "[ISO-8859-1] Åke Sandgren" <ake.sandgren at hpc2n.umu.se>
> To: Lei Chai <chail at cse.ohio-state.edu>
> Cc: Dhabaleswar Panda <panda at cse.ohio-state.edu>,
>     mvapich-core at cse.ohio-state.edu
> Subject: Re: [mvapich-discuss] Assertion failure in mvapich 1.2rc2
>
> On Thu, 2008-09-11 at 20:47 +0200, Åke Sandgren wrote:
>> On Thu, 2008-09-11 at 11:17 -0700, Lei Chai wrote:
>> > Hi,
>> >
>> > To use the debug mode of mvapich2, you can use this configure option:
>> >
>> > ./configure --enable-g=dbg
>> >
>> > Then when you run the program, you can use "mpirun_rsh -debug" or
>> > "mpiexec -gdb", then I think you will be able to get core dump by gdb
>> > commands like "generate-core-file". Alternatively, you can replace the
>> > assertion in the code with an artificial segfault, and see the backtrace.
>>
>> What i want is for the code to drop a core-file by itself when running
>> through the batchsystem not through use of any debugger. It's a real
>> pain running a debugger on anything with more then 4 tasks.
>> (And our ddt license is for max 16 tasks so i can't use that either)
>
> Perhaps i should have been a bit more specifik. I want the mvapich to
> not catch SEGV itself and instead let the system drop core.
>
>