From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] vx32, 9vx 0.12
Date: Tue, 1 Jul 2008 10:44:51 -0700 [thread overview]
Message-ID: <3e1162e60807011044wb76e650y79a6a097ff8be5f8@mail.gmail.com> (raw)
In-Reply-To: <20080701173425.26E701E8C1F@holo.morphisms.net>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Tue, Jul 1, 2008 at 10:36 AM, Russ Cox <rsc@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:
[8:28] dave(mt64):..p/9vx-0.12 %> ./9vx.OSX
247 ssh2 fault 0 no segment
258 ssh2 fault 0 no segment
ssh2 can be found in /n/sources/contrib/john and it works very nicely for
my needs so far.
[-- Attachment #2: Type: text/html, Size: 1495 bytes --]
next prev parent reply other threads:[~2008-07-01 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 14:53 Russ Cox
2008-07-01 16:06 ` [9fans] " David Leimbach
2008-07-01 16:20 ` David Leimbach
2008-07-01 17:36 ` Russ Cox
2008-07-01 17:44 ` David Leimbach [this message]
2008-07-01 17:05 ` Bakul Shah
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=3e1162e60807011044wb76e650y79a6a097ff8be5f8@mail.gmail.com \
--to=leimy2k@gmail.com \
--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).