-
Hi, I'm trying the hello world code of DPCPP book, and I tried the code at https://github.com/Apress/data-parallel-CPP/blob/main/samples/Ch01_intro/fig_1_1_hello.cpp, but met crash when debug the program with gdb, see below. I also tried with .../intel/oneapi/debugger/10.1.2/gdb/intel64/bin/gdb-oneapi, the same issue.
btw, Intel gpu is selected by the queue as default. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
@guoyejun this sounds like a bug to me, so I transferred this discussion to issues: #4331 |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
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.