From: arisawa@ar.aichi-u.ac.jp
To: 9fans@nx.aichi-u.ac.jp
Subject: [9fans] snoopy is broken
Date: Sat, 15 Jun 2002 15:50:52 +0900 [thread overview]
Message-ID: <20020615065057.434ED19999@mail.cse.psu.edu> (raw)
Hello,
Snoopy enters broken state in some condition.
Probably, large traffic make a problem.
Kenji Arisawa
#
# In one windows
#
term% snoopy -sf tcp>/dev/null
#
# In other windows
#
term% ls -l /n/nx/home/arisawa/src
--rw-r--r-- M 87 arisawa wheel 62812 Feb 7 1996
/n/nx/home/arisawa/src/zmodem.tar.gz
term% cat /n/nx/home/arisawa/src/zmodem.tar.gz>/dev/null
#
# Then snoopy is broken
#
snoopy 1826: suicide: sys: trap: fault read addr=0x7ffff000
pc=0x0000d170
#
# stack of acid
#
term% acid 1826
/proc/1826/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk()
At pc:0x0000d170:fcallfmt+0x352 /sys/src/libc/9sys/fcallfmt.c:61
fcallfmt(fmt=0x7fffed64) /sys/src/libc/9sys/fcallfmt.c:12
called from _fmtdispatch+0x94 /sys/src/libc/fmt/fmt.c:175
buf=0x6c617754
e=0x7fffece4
f=0x7fffedd8
tag=0x0000d171
tmp=0x00000000
i=0x00000085
p=0x7fffeaf4
q=0x7fffee18
d=0x7fffea1c
_fmtdispatch(isrunes=0x00000000,f=0x7fffed64,fmt=0x000167ae)
/sys/src/libc/fmt/fmt.c:113
called from dofmt+0x75 /sys/src/libc/fmt/dofmt.c:62
rune=0xb6b30046
dofmt(fmt=0x000167ac,f=0x7fffed64) /sys/src/libc/fmt/dofmt.c:7
called from vseprint+0x5d /sys/src/libc/fmt/vseprint.c:20
nfmt=0x00000000
rt=0x7fffede4
rs=0x7fffee54
r=0x0000c563
rune=0xa7b20000
t=0x0002c9c8
s=0x000308f6
n=0x00340000
vseprint(e=0x000308f7,buf=0x0002c9c8,args=0x7fffedc8,fmt=0x000167ac)
/sys/src/libc/fmt/vseprint.c:6
called from seprint+0x2b /sys/src/libc/fmt/seprint.c:13
f=0x7fffee00
seprint(fmt=0x000167ac,buf=0x0002c9c8,e=0x000308f7)
/sys/src/libc/fmt/seprint.c:6
called from p_seprint+0x8c /sys/src/cmd/ip/snoopy/ninep.c:32
args=0x7fffedc8
p_seprint(m=0x7fffef1c) /sys/src/cmd/ip/snoopy/ninep.c:21
called from printpkt+0x131 /sys/src/cmd/ip/snoopy/main.c:271
f=0x0000006e
p=0x0002c9c8
printpkt(p=0x0002c8f8,e=0x000308f7,ps=0x0001c87a,pe=0x0001ccb0)
/sys/src/cmd/ip/snoopy/main.c:256
called from main+0x49f /sys/src/cmd/ip/snoopy/main.c:180
m=0x0001c8b0
main(argv=0x7fffefe4,argc=0x00000000)
/sys/src/cmd/ip/snoopy/main.c:48
called from _main+0x31 /sys/src/libc/386/main9.s:16
pkt=0x0001c87a
buf=0x0002c8f8
e=0x000308f7
_argc=0x00000066
_args=0x00019250
p=0x7fffeff8
file=0x00019267
cfd=0x00000004
fd=0x00000005
n=0x00000436
acid:
next reply other threads:[~2002-06-15 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 6:50 arisawa [this message]
2002-06-15 13:03 presotto
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=20020615065057.434ED19999@mail.cse.psu.edu \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@nx.aichi-u.ac.jp \
/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).