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/59433] [4.9 regression] Many 64-bit Go tests SEGV on Solaris
Date: Thu, 09 Jan 2014 12:50:00 -0000	[thread overview]
Message-ID: <bug-59433-4-08DnS6mZEU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59433-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59433

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #3 from Ian Lance Taylor <ian at airs dot com> ---
> Should be fixed now.

I'm seeing a massive improvement, but now some 32-bit tests that used to
work before are failing:

 Running target unix
+FAIL: net
 FAIL: runtime
-FAIL: os/user
+FAIL: log/syslog
+FAIL: net/http
 FAIL: sync/atomic

The net failure is another instance of PR go/59431, which I still need
to analyse, but the log/syslog and net/http failures are different.
They both SEGV like this:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 3 (LWP 3)]
0xfe0f8a9f in runtime_netpoll (block=block@entry=1 '\001')
    at /vol/gcc/src/hg/trunk/local/libgo/runtime/netpoll_select.c:163
163             __builtin_memcpy(prfds, &fds, sizeof fds);
(gdb) where
#0  0xfe0f8a9f in runtime_netpoll (block=block@entry=1 '\001')
    at /vol/gcc/src/hg/trunk/local/libgo/runtime/netpoll_select.c:163
#1  0xfe0fd0ef in findrunnable ()
    at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:1653
#2  schedule () at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:1751
#3  0xfe0fd38a in runtime_mstart (mp=0x18511800)
    at /vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:1000
#4  0xfdd462fc in _thrp_setup () from /lib/libc.so.1
#5  0xfdd465a0 in ?? () from /lib/libc.so.1
#6  0x00000000 in ?? ()
(gdb) p prfds
$1 = (fd_set *) 0x0
(gdb) p fds
$2 = {fds_bits = {352, 0 <repeats 31 times>}}

I suspect they are related to PR go/59431, too: this should only happen
if runtime_SysAlloc returned NULL, which only happens for unhandled mmap
return value, although I don't see that in truss.  Need to investigate
in more detail.

    Rainer


  parent reply	other threads:[~2014-01-09 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 15:46 [Bug go/59433] New: " ro at gcc dot gnu.org
2013-12-09 15:47 ` [Bug go/59433] " ro at gcc dot gnu.org
2013-12-10 13:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-12-17 18:31 ` jakub at gcc dot gnu.org
2014-01-08  0:42 ` ian at gcc dot gnu.org
2014-01-08  0:43 ` ian at airs dot com
2014-01-09 12:50 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2014-01-09 14:30 ` ro at CeBiTec dot Uni-Bielefeld.DE

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-59433-4-08DnS6mZEU@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).