public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mariappan.balraj at gmail dot com" <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: Wed, 15 Feb 2023 05:54:27 +0000 [thread overview]
Message-ID: <bug-30038-4717-TGnr0RUC6u@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 #10 from mariappan balraj <mariappan.balraj at gmail dot com> ---
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.
next prev parent reply other threads:[~2023-02-15 5: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
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 [this message]
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-TGnr0RUC6u@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).