public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/64595] cgo installed into wrong directory Date: Tue, 20 Jan 2015 00:02:00 -0000 [thread overview] Message-ID: <bug-64595-4-EoTDYdRr5S@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64595-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595 --- Comment #10 from Ian Lance Taylor <ian at airs dot com> --- The point of libbacktrace, at least if you call the backtrace_full function, is to get file/line information. If you don't need file/line information, you can just use _Unwind_Backtrace.
next prev parent reply other threads:[~2015-01-20 0:02 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-14 8:42 [Bug go/64595] New: " rguenth at gcc dot gnu.org 2015-01-14 9:03 ` [Bug go/64595] " schwab@linux-m68k.org 2015-01-14 13:25 ` ian at airs dot com 2015-01-14 13:33 ` rguenther at suse dot de 2015-01-14 15:17 ` ian at airs dot com 2015-01-19 8:59 ` rguenther at suse dot de 2015-01-19 9:13 ` rguenth at gcc dot gnu.org 2015-01-19 23:44 ` ian at airs dot com 2015-01-19 23:55 ` schwab@linux-m68k.org 2015-01-20 0:00 ` pinskia at gcc dot gnu.org 2015-01-20 0:02 ` ian at airs dot com [this message] 2015-01-20 0:04 ` schwab@linux-m68k.org 2015-01-20 0:36 ` ian at airs dot com 2015-01-20 8:19 ` rguenther at suse dot de 2015-01-20 8:21 ` rguenther at suse dot de 2015-01-20 10:22 ` jakub at gcc dot gnu.org 2015-01-20 16:28 ` [Bug go/64595] go programs abort when debug info is stripped ian at airs dot com 2015-01-20 17:42 ` pinskia at gcc dot gnu.org 2015-01-23 1:43 ` ian at gcc dot gnu.org 2015-01-23 19:52 ` ian at gcc dot gnu.org 2015-01-23 22:27 ` ian at gcc dot gnu.org 2015-01-23 22:31 ` ian at airs dot com 2015-02-03 20:05 ` ian at airs 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-64595-4-EoTDYdRr5S@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).