From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28054 invoked by alias); 19 Jan 2015 23:44:08 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 28003 invoked by uid 48); 19 Jan 2015 23:44:03 -0000 From: "ian at airs dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/64595] cgo installed into wrong directory Date: Mon, 19 Jan 2015 23:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ian at airs dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com 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: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg01938.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595 --- Comment #7 from Ian Lance Taylor --- That failure is not related to the new gotools. I expect it would happen with any Go program. Go requires that there be enough debug info to do a stack backtrace with file/line information. It uses the libbacktrace library, but that library doesn't understand separate debuginfo sections. I can fix this specific problem so that the program is more likely to run, but in general Go code expects to be able to get that backtrace and most real Go programs will fail without it. I guess I or somebody needs to fix libbacktrace to understand separate debuginfo objects.