public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/52583] Several new go testsuite failues on Solaris
Date: Fri, 13 Jun 2014 13:56:00 -0000 [thread overview]
Message-ID: <bug-52583-4-nM8fDoZhkD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52583-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52583
--- Comment #29 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Fri Jun 13 13:56:14 2014
New Revision: 211640
URL: https://gcc.gnu.org/viewcvs?rev=211640&root=gcc&view=rev
Log:
PR go/52583
runtime: Stop backtrace at a few recognized functions.
On x86_64 Solaris the makecontext function does not properly
indicate that it is at the top of the stack. Attempting to
unwind the stack past a call to makecontext tends to crash.
This patch changes libgo to look for certain functions that
are always found at the top of the stack, and to stop
unwinding when it reaches one of those functions. There is
never anything interesting past these functions--that is,
there is never any code written by the user.
Modified:
trunk/libgo/runtime/go-callers.c
next prev parent reply other threads:[~2014-06-13 13:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 11:48 [Bug go/52583] New: " ro at gcc dot gnu.org
2012-03-14 20:39 ` [Bug go/52583] " ubizjak at gmail dot com
2012-03-15 5:36 ` ian at airs dot com
2012-03-15 7:25 ` ubizjak at gmail dot com
2012-03-15 16:37 ` ian at airs dot com
2012-03-15 23:46 ` ubizjak at gmail dot com
2012-03-16 3:21 ` ian at airs dot com
2012-03-16 8:47 ` ubizjak at gmail dot com
2012-03-16 10:01 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-03-16 11:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-03-16 11:14 ` ubizjak at gmail dot com
2012-03-17 16:42 ` ubizjak at gmail dot com
2012-03-17 17:04 ` ian at airs dot com
2012-03-17 17:20 ` ubizjak at gmail dot com
2012-03-17 17:24 ` ubizjak at gmail dot com
2012-03-20 14:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-04-24 20:44 ` ian at airs dot com
2012-04-25 4:26 ` ian at gcc dot gnu.org
2012-04-25 4:27 ` ian at gcc dot gnu.org
2012-04-25 4:29 ` ian at airs dot com
2012-04-25 6:41 ` ubizjak at gmail dot com
2012-04-25 14:58 ` ian at airs dot com
2012-04-27 16:42 ` ian at airs dot com
2012-08-26 6:59 ` ubizjak at gmail dot com
2012-08-26 7:53 ` ubizjak at gmail dot com
2012-08-26 8:41 ` pinskia at gcc dot gnu.org
2012-09-06 5:28 ` ian at gcc dot gnu.org
2012-09-06 5:28 ` ian at gcc dot gnu.org
2012-09-06 5:29 ` ian at gcc dot gnu.org
2012-09-06 5:30 ` ian at airs dot com
2014-06-13 13:56 ` ian at gcc dot gnu.org [this message]
2014-06-13 13:58 ` 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-52583-4-nM8fDoZhkD@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: 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).