From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 Go 386
Date: Sat, 25 May 2013 07:50:00 +0200 [thread overview]
Message-ID: <1254af8db321f876dc44170675d6df34@proxima.alt.za> (raw)
In-Reply-To: <CAOr72mjCX7A2qnnJQO+Yfo2KEkkG5S7n9jgU=ErNcLq6sBoVvw@mail.gmail.com>
I've seen this before, although by now I've seen so many errors crop
up that I can't recall them all.
>> === RUN TestErrors-2
>> template.test 289408: suicide: sys: floating point in note handler pc=0x0001e9c7
>> exit status: 'template.test 289408: sys: floating point in note
>> handler pc=0x0001e9c7'
>> FAIL html/template 0.213s
>
> acid: stk()
> runtime.memmove(to=0x106dd000,fr=0x30887660,n=0x2c)+0x107
> /usr/glenda/src/go/src/pkg/runtime/memmove_386.s:145
> runtime.sighandler(s=0x30887660,v=0x308876e4,gp=0x106d31b0)+0x126
> /usr/glenda/src/go/src/pkg/runtime/os_plan9_386.c:67
> runtime.sigtramp(ureg=0x30887660,note=0x106d31b0)+0x44
> /usr/glenda/src/go/src/pkg/runtime/sys_plan9_386.s:161
> 0x308876e4 ?file?:0
> acid:
I am surprised, but also relieved that we have a resproducible mistake
outside the run.rc scope. We can focus on that.
I'm hoping cinap, with his in-depth knowledge of the kernel, can shed
some light here. It does look as if we have some error in the
handling of syscalls or notes, although I already mentioned I expected
a note to a process that had received a floating point exception
rather than a floating point exception in a note handler.
In my most recent copy of src/go/src/pkg/runtime/sys_plan9_386.s line
161 is a get_tls(BX), on return from sighandler(). Get_tls on the 386
resolves to
MOVL _tos(SB),r // zasm_plan9_386.h:8
so unless SB is way off, it does not seem to be a problem. I'd lay my
bets on sighandler() (so_plan9_386.c:28), but I am not comfortable
digging in there.
++L
next prev parent reply other threads:[~2013-05-25 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 22:14 Christopher Nielsen
2013-05-23 23:25 ` Steve Simon
2013-05-24 13:50 ` erik quanstrom
2013-05-24 14:29 ` lucio
2013-05-25 1:11 ` Jeremy Jackins
2013-05-25 2:00 ` Skip Tavakkolian
2013-05-25 2:36 ` Jeremy Jackins
2013-05-25 3:06 ` Jeremy Jackins
2013-05-25 5:50 ` lucio [this message]
2013-05-25 12:53 ` erik quanstrom
2013-05-25 18:25 ` Jeremy Jackins
2013-05-25 5:17 ` lucio
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=1254af8db321f876dc44170675d6df34@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).