Maciej Marek wrote:
> U¿ytkownik Brian Barrett <brbarret_at_[hidden]> wrote:
>
>> Can you run with just one process? If not (and I'm guessing not),
>
> No, I can't. The same happens with just one process...
>
>
>> can you try running under a debugger and seeing where the failure is
>> occurring? As long as you've already run lamboot, you should be able
>> to do something like:
>>
>> gdb ./myprog
>>
>> And run under a debugger to see where the failure occurs.
>
>
> Here's the output of gdb:
>
> ----------------------------------------------------------------
> (gdb) run
> Starting program: /home/macmar/Nauka/Fortran/mpi/myprog
> [Thread debugging using libthread_db enabled]
> [New Thread -1212262720 (LWP 30967)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1212262720 (LWP 30967)]
> __pthread_atfork (prepare=0x805df40 <ptmalloc_lock_all>, parent=0x805dfd0 <ptmalloc_unlock_all>, child=0x805def0 <ptmalloc_unlock_all2>)
> at pthread_atfork.c:57
> 57 pthread_atfork.c: No such file or directory.
> in pthread_atfork.c
> (gdb) step
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> The program no longer exists.
> (gdb)
> ------------------------------------------------------------------------
>
> I'm not familiar with gdb, so I don't know how to track
> down the real source of the error.
>
If you want to use source debugging inside libpthread, you will need the
source code corresponding with your build of that library. Short of
that, use bt to find out where it comes from in your source, and check
the arguments you are passing. The fault is likely to come from a bad
argument.
|
