From: "Russ Cox" <rsc@swtch.com>
To: alltom@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] tip 9vx segfault on Ubuntu in Xen
Date: Tue, 1 Jul 2008 09:00:50 -0400 [thread overview]
Message-ID: <20080701125833.8AD771E8C45@holo.morphisms.net> (raw)
In-Reply-To: <326364c20806301953k7fa2ebf9i1c7f3049a210bf39@mail.gmail.com>
> I have Ubuntu on a VPS (on Xen) and I'd like to install a Plan 9
> server using 9vx. 9vx tip compiles, but segfaults after the "256M
> memory" line (as does the precompiled binary, in the same place). I am
> tunneling to local X11 on OS X 10.5.3.
>
> I don't know how to debug this properly, but here is gdb output
> similar to what I saw in another report.
The seg faults are normal. 9vx handles them and continues.
To run under gdb you need to say
handle SIGSEGV noprint nostop
so that gdb will let it keep going.
What behavior did you see when you weren't running under gdb?
If it was a panic, better to set a break point at panic.
Russ
next prev parent reply other threads:[~2008-07-01 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 2:53 Tom Lieber
2008-07-01 13:00 ` Russ Cox [this message]
2008-07-01 14:02 ` Tom Lieber
2008-07-01 14:13 ` Russ Cox
2008-07-01 15:02 ` Tom Lieber
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=20080701125833.8AD771E8C45@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=alltom@gmail.com \
/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).