On Thu, Jan 5, 2023 at 10:39 PM mariappan balraj <mariappan.bal...@gmail.com> wrote: > > When I call the same function from pure C code, I am able to get the complete > stack and it is not reporting that the stack is corrupted. I am expecting the > same C stack when I use CGO also. Please kindly help with this.
C code and Go code run on different stacks. As I tried to explain earlier, gdb does not have enough information to unwind from a C stack to a Go stack. What you are looking for simply doesn't work. Sorry. 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/CAOyqgcWyB1iJXZLCx722QKgOp4Tr-g670saGSz2DGbiKhoDRmA%40mail.gmail.com.
