public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/51874] Many libgo testsuite failures on Solaris, IRIX Date: Fri, 27 Jan 2012 13:04:00 -0000 [thread overview] Message-ID: <bug-51874-4-r2s9YfD2a4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51874-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51874 --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-01-27 12:52:29 UTC --- The chan.go testcase also fails on 32-bit IRIX, but in a different way: > ./chan.x panic: runtime error: invalid memory address or nil pointer dereference Running it under gdb, I find: Program received signal SIGSEGV, Segmentation fault. runtime_mcall (pfn=0x823198 <schedule>) at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:283 283 if (g == nil || !g->fromgogo) { (gdb) where #0 runtime_mcall (pfn=0x823198 <schedule>) at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:283 #1 0x0081b9e0 in runtime_chanrecv (t=<optimized out>, c=0x2030b000, ep=0x20102f60 "", selected=0x0, received=0x0) at /vol/gcc/src/hg/trunk/local/libgo/runtime/chan.c:333 #2 0x0081bae0 in __go_receive_small (t=<optimized out>, c=<optimized out>) at /vol/gcc/src/hg/trunk/local/libgo/runtime/chan.c:432 #3 0x10002418 in main.main () at /vol/gcc/src/doc/bugs/chan.go:10 #4 0x00822994 in runtime_main () at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:371 #5 0x00823960 in kickoff () at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:237 #6 0x0faee6d0 in _sethostname () from /usr/lib32/libc.so.1 #7 0x008225f4 in runtime_mcall (pfn=0x823198 <schedule>) at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:281 #8 0x00000000 in ?? () It may be an issue that IRIX is an emutls target. On 64-bit IRIX, I get > ./chan.x64 panic: 0 as on Solaris/SPARC. Rainer
next prev parent reply other threads:[~2012-01-27 12:53 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-16 18:11 [Bug go/51874] New: " ro at gcc dot gnu.org 2012-01-27 12:18 ` [Bug go/51874] " ro at gcc dot gnu.org 2012-01-27 12:35 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-27 13:04 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2012-01-31 19:01 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-11 0:07 ` ian at airs dot com 2012-02-12 6:01 ` ian at gcc dot gnu.org 2012-02-12 6:05 ` ian at airs dot com 2012-02-12 6:06 ` ian at airs dot com 2012-02-12 6:55 ` pinskia at gcc dot gnu.org 2012-02-14 18:20 ` ian at airs dot com 2012-02-14 18:32 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-16 7:31 ` ian at gcc dot gnu.org 2012-02-16 19:46 ` [Bug go/51874] Many libgo testsuite failures on IRIX ro at gcc dot gnu.org 2012-03-22 8:57 ` rguenth at gcc dot gnu.org 2012-04-04 11:49 ` ro at gcc dot gnu.org 2012-04-24 16:33 ` ian at airs dot com 2012-05-08 15:10 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-05-08 15:20 ` ro at gcc dot gnu.org 2012-07-02 14:10 ` rguenth at gcc dot gnu.org 2014-06-13 11:41 ` ro at gcc dot gnu.org
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-51874-4-r2s9YfD2a4@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).