Re: [Starpu-devel] [segfault debugging]

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

Hello,

Maxim Abalenkov, on lun. 29 janv. 2018 12:28:20 +0000, wrote:
> As I understand, something is wrong with the worker’s task dependencies. 
> But I
> would like to find the line of __my__ code that is causing the trouble. Do 
> you
> possibly know, how to find that out? The “backtrace (bt)” command is not
> helpful in this case. Thank you!

Since the backtrace is at the end of the execution of the task, it's
on a different thread than the submission thread, thus backtrace is
useless. You can however inspect j->task (you can use starpu's gdbinit
to get the starpu-print-task gdb command) to see what the task looks
like, and from that infer what submitted it.

I'm realizing that it could be useful, in debugging mode, to record the
backtrace on task submission, so that one can get it later on. Yet
another item on the TODO list.

Samuel