[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 #11 from mariappan balraj <mariappan.balraj at gmail dot com> ---
Hi,

I am seeing some difference between what BT you are getting in and what I
am getting. In your case, libgo.so got used. But in my case it is not. I am
trying to understand what makes this difference. Could you please share the
following information? This will help me to progress further.

1) GO version
2) Build steps?
3) output of go env command
4) Output of "go version -m <go_binary>"

#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

#8  0x00000000004411e5 in runtime.dieFromSignal (sig=6) at
/usr/lib/go-1.18/src/runtime/signal_unix.go:852
#9  0x000000000042dca9 in runtime.crash () at
/usr/lib/go-1.18/src/runtime/signal_unix.go:944
#10 runtime.fatalpanic (msgs=<optimized out>) at
/usr/lib/go-1.18/src/runtime/panic.go:1092
#11 0x000000000042d477 in runtime.gopanic (e=...) at
/usr/lib/go-1.18/src/runtime/panic.go:941

Best Regards
Mariappan

On Wed, Feb 15, 2023 at 11:24 AM mariappan balraj <
mariappan.balraj@gmail.com> wrote:

> Hi,
>
> I am seeing the same behaviour even in red hat linux. It is good if you
> can share your go environment and the steps you are following to build it.
> So that I can try. If that solves the issue then it is really nice. Kindly
> please help.
>
> Best Regards
> Mariappan
>
> On Tue, Feb 14, 2023 at 11:09 PM tromey at sourceware dot org <
> sourceware-bugzilla@sourceware.org> wrote:
>
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30038
>>
>> --- Comment #9 from Tom Tromey <tromey at sourceware dot org> ---
>> Sorry, I can't check on Ubuntu for you.
>> I think you will have to look more deeply into it yourself somehow.
>> Normally a core file shouldn't affect the backtrace.
>> So I suspect something is weird in your environment, like
>> maybe you compiled something with optimization or LTO or the like.
>>
>> --
>> You are receiving this mail because:
>> You are on the CC list for the bug.
>> You reported the bug.
>
>

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