On Thu, Dec 22, 2022 at 1:57 PM mariappan balraj <mariappan.bal...@gmail.com> wrote: > > I have following programming where making CGO from GO code. test3() is called > from Go code. Which calls test2() and which calls test1(). In test1(), there > is a NULL pointer assignment. I could able to generate the core dump when > running the program. But when I use gdb, I am not getting the stack trace. > Can someone please help?
The call from Go to C switches stacks. The Go runtime doesn't provide enough information for gdb to be able to unwind past that stack switch. gdb can show the stack trace of the C function calls, but not the stack trace of the Go functions. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWgwnAx1zce2K4jLoSNLOO2WX5u5BJ9E5W%2B3mxRu3rGrw%40mail.gmail.com.
