public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [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.
Date: Tue, 14 Feb 2023 07:54:00 +0000 [thread overview]
Message-ID: <bug-30038-4717-gnfaHtSFqW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30038-4717@http.sourceware.org/bugzilla/>
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 are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-14 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 6:54 [Bug go/30038] New: " mariappan.balraj at gmail dot com
2023-01-24 6:55 ` [Bug go/30038] " mariappan.balraj at gmail dot com
2023-01-24 13:09 ` tromey at sourceware dot org
2023-01-25 5:22 ` mariappan.balraj at gmail dot com
2023-02-06 5:51 ` mariappan.balraj at gmail dot com
2023-02-13 9:41 ` mariappan.balraj at gmail dot com
2023-02-14 6:12 ` tromey at sourceware dot org
2023-02-14 6:28 ` mariappan.balraj at gmail dot com
2023-02-14 7:54 ` tromey at sourceware dot org [this message]
2023-02-14 10:29 ` mariappan.balraj at gmail dot com
2023-02-14 17:39 ` tromey at sourceware dot org
2023-02-15 5:54 ` mariappan.balraj at gmail dot com
2023-02-15 11:24 ` mariappan.balraj at gmail dot com
2023-02-15 18:17 ` tromey at sourceware dot org
2023-02-16 23:38 ` ian at airs dot com
2023-02-17 1:21 ` tromey at sourceware dot org
2023-02-22 5:10 ` mariappan.balraj at gmail dot com
2023-02-28 1:40 ` tromey at sourceware dot org
2023-04-03 11:59 ` mariappan.balraj at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30038-4717-gnfaHtSFqW@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).