Stack trace and signal abort debugging with gdb

Hello everyone,

I am working on some detection project and after running the source code for about a minute , it aborts and I tried to debug it and still facing error.
It says even the backtrace also stopped due to corrupt stack.

class_name = person
ObjectDet->person
F0223 14:47:41.367681 2996 math_functions.cu:79] Check failed: error == cudaSuccess (4 vs. 0) unspecified launch failure
*** Check failure stack trace: ***

Program received signal SIGABRT, Aborted.
__libc_do_syscall () at …/ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
44 …/ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory.
(gdb) bt
#0 __libc_do_syscall () at …/ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
#1 0xf76dcebe in __GI_raise (sig=sig@entry=6) at …/nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xf76df716 in __GI_abort () at abort.c:89
#3 0xf2bc6028 in ?? () from /usr/lib/arm-linux-gnueabihf/libglog.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Any advice on this and guidance.

Hi,

Thanks for your question.
We are investigating this issue, will update to you later.

Hello AastaLLL,

Any update or opinion on what error I am facing and how could I overcome it to progress.

Hi,

Sorry for the late reply.

It’s hard for us to debug this without source code.
Could you share the source code of math_functions.cu for us better investigation.

You can send a private message.