From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] problems with tracing 9vx on os x (was: Re: ghostscript not finding LucidaSans
Date: Mon, 28 Jun 2010 14:05:14 -0400 [thread overview]
Message-ID: <2443C2E0-C7B8-4819-B09C-8229DBCFE7EF@mac.com> (raw)
In-Reply-To: <AANLkTik3urgfu2RgGo0Rf_PG5eEdZ-A8gdNud4TAL-QX@mail.gmail.com>
On Jun 28, 2010, at 11:04 AM, ron minnich wrote:
> well, once again, ratrace can be a good tool for understanding things
> that don't make sense. I use it all the time for this type of problem
> and the results are frequently illuminating.
>
> ron
>
First I found a slight building problem on Mac OS X 10.5.8: ethertap.c
needs to be changed to include <sys/socket.h> before <net/if.h> and to
add a defined(__MACOSX__) or similar to the #elf defined(__FreeBSD__)
so opentap() can be defined.
However once this version was built, I got the following right after
seeing the memory usage statistic line:
9vx panic: user fault: signo=10 addr=1100cc77 [useraddr=cc77] read=1
eip=b7de5 esp=2e93ece0
sleeping, so you can attach gdb to pid 44257
next prev parent reply other threads:[~2010-06-28 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 1:07 [9fans] " Pietro Gagliardi
2010-06-28 1:56 ` erik quanstrom
2010-06-28 3:18 ` Pietro Gagliardi
2010-06-28 4:40 ` erik quanstrom
2010-06-28 6:24 ` Pietro Gagliardi
2010-06-28 6:36 ` Pietro Gagliardi
2010-06-28 13:09 ` erik quanstrom
2010-06-28 14:23 ` Pietro Gagliardi
2010-06-28 15:04 ` ron minnich
2010-06-28 18:05 ` Pietro Gagliardi [this message]
2010-06-29 8:03 ` [9fans] problems with tracing 9vx on os x (was: " yy
2010-06-29 14:31 ` Pietro Gagliardi
2010-06-28 12:21 ` [9fans] " Ethan Grammatikidis
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=2443C2E0-C7B8-4819-B09C-8229DBCFE7EF@mac.com \
--to=pietro10@mac.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).