Re: [Starpu-devel] segfault MPI execution and starpu_fxt_tool

[Samuel Thibault <samuel.thibault@inria.fr>]

Does it work on plafrim1?

How can I connect to plafrim2?

Florent Pruvost, le Fri 26 Jun 2015 16:43:10 +0200, a écrit :
> (gdb) bt
> #0  0x00007ffff63c4a94 in vfprintf () from /lib64/libc.so.6
> #1  0x00007ffff63cdb77 in fprintf () from /lib64/libc.so.6
> #2  0x00007ffff7b7ece6 in _starpu_fxt_dag_set_task_done (job_id=<optimized
> out>, label=<optimized out>, color=<optimized out>) at
> ../../src/debug/traces/starpu_fxt_dag.c:97

I guess the problematic pointer is the "name" pointer? What is the
content of the ev struct, which is the source of this pointer? The trace
files themselves dont't show anything odd: when param[3] is 1, param[4]
always contain a name, so it shouldn't segfault.

Samuel