|
|
 Up |
|
|
  |
Author: Russ CoxRuss Cox Date: Jul 1, 2008 07:56
There are new sources and binaries in the usual places.
If you missed the announcement before, there is now
a Mercurial repository at http://hg.pdos.csail.mit.edu/hg/vx32/
The OS X code seems to have stabilized, and it doesn't
require X11 anymore. I think there are OS X bugs tickled
by having signals flying all over the place: I've seen both
pthread_cond_wait and pipe read miss the corresponding
pthread_cond_signal or pipe write. If someone who is
knowledgeable wants to take a look, see 9vx/sched.c.
I've worked around the bugs, so you shouldn't see hangs
anymore. You might see the occasional 1-second hiccup.
Russ
|
| |
|
| | 5 Comments |
|
|
|
|
|
Author: David LeimbachDavid Leimbach Date: Jul 1, 2008 09:23
On Tue, Jul 1, 2008 at 9:06 AM, David Leimbach gmail.com> wrote:
>
>
> On Tue, Jul 1, 2008 at 7:53 AM, Russ Cox swtch.com> wrote:
>>> There are new sources and binaries in the usual places.
>>
>> If you missed the announcement before, there is now
>> a Mercurial...
|
| Show full article (2.77Kb) |
| 2 Comments |
|
|
Date: Jul 1, 2008 10:09
On OSX 9vx consistently sigsegv panics if you quickly resize
its window a few times, particluarly before it finishes
repainting. This doesn't happen (or is hard to trigger) when
rio is not up.
Running it under gdb reveals:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
[Switching to process 832 thread 0x5c43]
0x00000000 in ?? ()
(gdb) where
#0 0x00000000...
|
| Show full article (1.89Kb) |
| no comments |
|
|
Author: Russ CoxRuss Cox Date: Jul 1, 2008 10:39
>> 247 ssh2: unhandled fault va=0 [1100000] eip=bee1b
>> cpu0: registers for ssh2 247
>> FLAGS=0 TRAP=0 ECODE=0 PC=BEE1B USP=FFFFF00
>> AX 00000000 BX 001339C1 CX FFFFFFFF DX 000FF2F2
>> SI FFFFFFFF DI 00000000 BP 00000000
As long as only ssh2 crashed, this doesn't bother me too much.
9vx does get a little chatty in that case, but that doesn't bother
me for now.
Can you test whether running ssh2 without factotum also dies
on native Plan 9? I have no ssh2 binary.
Russ
|
| |
| 1 Comment |
|
|
|
|
|
Author: David LeimbachDavid Leimbach Date: Jul 1, 2008 10:48
On Tue, Jul 1, 2008 at 10:36 AM, Russ Cox swtch.com> wrote:
>>> 247 ssh2: unhandled fault va=0 [1100000] eip=bee1b
>>> cpu0: registers for ssh2 247
>>> FLAGS=0 TRAP=0 ECODE=0 PC=BEE1B USP=FFFFF00
>>> AX 00000000 BX 001339C1 CX FFFFFFFF DX 000FF2F2
>>> SI FFFFFFFF DI 00000000 BP 00000000
>
> As long as only ssh2 crashed, this doesn't bother me too much.
> 9vx does get a little chatty in that case, but that doesn't bother
> me for now.
>
> Can you test whether running ssh2 without factotum also dies
> on native Plan 9? I have no ssh2 binary.
>
> Russ
>
> Yes only ssh2 is crashing... it didn't do this before .12 to the best of my
recollection, that I'm getting SEGV errors on my terminal where I started
9vx seems important too:
|
| Show full article (1.91Kb) |
| no comments |
|
|
