[Bug go/30038] When using CGO and C code is calling GO function, not getting call stack of C from core dump. Only getting call stack of GO.

["mariappan.balraj at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30038

--- Comment #8 from mariappan balraj <mariappan.balraj at gmail dot com> ---
Hi,

I am really happy with your continuous support on this issue. It is good
that it is working in Fedora 36. I am using UBUNTU for my testing. Is it
possible to check the behaviour in UBUNTU also? I was following this issue
with the official GO team also. They also said that it is the problem with
GDB. GDB works well in Fedora and not in UBUNTU also is a compatible issue
with GDB right?

https://github.com/golang/go/issues/57698

Best Regards
Mariappan

On Tue, Feb 14, 2023 at 1:24 PM tromey at sourceware dot org <
sourceware-bugzilla@sourceware.org> wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=30038
>
> --- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
> This also works for me:
>
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `./test'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x00007fcf8468ec0c in __pthread_kill_implementation () from
> /lib64/libc.so.6
> [Current thread is 1 (Thread 0x7fcf8667a1c0 (LWP 1993139))]
> (gdb) bt
> #0  0x00007fcf8468ec0c in __pthread_kill_implementation () from
> /lib64/libc.so.6
> #1  0x00007fcf8463e986 in raise () from /lib64/libc.so.6
> #2  0x00007fcf85b2ae84 in runtime[dieFromSignal] () from /lib64/libgo.so.21
> #3  0x00007fcf85b54f00 in runtime[sigtrampgo] () from /lib64/libgo.so.21
> #4  0x00007fcf855f1bf8 in runtime[sigtramp] () from /lib64/libgo.so.21
> #5  <signal handler called>
> #6  0x00007fcf8468ec0c in __pthread_kill_implementation () from
> /lib64/libc.so.6
> #7  0x00007fcf8463e986 in raise () from /lib64/libc.so.6
> #8  0x00007fcf85b2ae84 in runtime[dieFromSignal] () from /lib64/libgo.so.21
> #9  0x00007fcf85b2aeee in runtime[crash] () from /lib64/libgo.so.21
> #10 0x00007fcf85b5e405 in runtime[gopanic] () from /lib64/libgo.so.21
> #11 0x000000000040475e in main.Test4 () at
> /home/tromey/gdb/PRS/pr-30038-go-bug/export.go:7
> #12 0x00000000004047ac in main.Cgoexp__Test4 () at
> /tmp/go-build/b001/_cgo_gotypes.go:34
> #13 0x0000000000405040 in test1 () at
> /home/tromey/gdb/PRS/pr-30038-go-bug/test.go:9
> #14 0x0000000000405060 in test2 () at
> /home/tromey/gdb/PRS/pr-30038-go-bug/test.go:14
> #15 0x0000000000405080 in test3 () at
> /home/tromey/gdb/PRS/pr-30038-go-bug/test.go:19
> #16 0x00000000004050a0 in _cgo_5bc4e3e20e89_Cfunc_test3 () at
> /tmp/go-build/cgo-gcc-prolog:46
> #17 0x0000000000404ed8 in main.__Cfunc__test3 () at
> /tmp/go-build/b001/_cgo_gotypes.go:25
> #18 0x0000000000404f54 in main.main () at
> /home/tromey/gdb/PRS/pr-30038-go-bug/test.go:25
>
>
> I'm using the system 'go' on Fedora 36.
> Perhaps it's some other issue in your environment.
> It doesn't seem to be a gdb bug.
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.