From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9E9223858C60; Wed, 15 Feb 2023 18:17:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9E9223858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676485039; bh=V/vpEZCrRD2gvRrXuv6oj4OqSx/3xa/s7MSTeDDGDs8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vNiMex5uNIMCF5/PZLfNOnC2ECrQLya2xSK5p2AcX+cwdvHc1i+pVbxW6w0Kpq4bw b9g+bFfeHWHGTUvFTmwwVCfS1ac1XM/8HQ9Ilbh2zi5UtL2tV2AvgUZLKlQ1iMFaSL QbtAtaCQg8VCf4Nlko75h47zy0RVMO/9UkPCgEqo= From: "tromey at sourceware dot 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 18:17:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: go X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30038 --- Comment #12 from Tom Tromey --- (In reply to mariappan balraj from comment #11) > Created attachment 14686 [details] > attachment-2197679-0.html >=20 > Hi, >=20 > 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 t= he > following information? This will help me to progress further. >=20 > 1) GO version > 2) Build steps? > 3) output of go env command > 4) Output of "go version -m " I'll try to get this later, but for the build steps I just did exactly what you wrote in comment #2. --=20 You are receiving this mail because: You are on the CC list for the bug.=