Skip to content

unable to debug malloc_shared with gdb #4330

Answered by abijaz
guoyejun asked this question in Q&A
Discussion options

You must be logged in to vote

For the Seg fault issue Applications that use unified shared memory (USM) may appear as raising a SIGSEGV when a USM-allocated memory is being accessed. This is a mechanism used by the runtime to trigger memory migration. In such cases, sending the signal back to the application resumes the program. For this, use GDB's signal SIGSEGV command which should resume the program.
Also in case of issue please provide gdb-oneapi logs.

Replies: 2 comments 5 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
5 replies
@guoyejun
Comment options

@abijaz
Comment options

@guoyejun
Comment options

@abijaz
Comment options

@guoyejun
Comment options

Answer selected by alexbatashev
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants