From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] gping crash
Date: Sat, 8 Sep 2001 19:35:46 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0109081929570.3418-100000@athena> (raw)
I've gotten gping to crash on me multiple times.
I thought I'd send it out in the event someone has the spare
cycles to solve the problem.
Cheers,
Sam
$C
treelookupgt(size=0x40, t=0x27ab0) /sys/src/libc/port/pool.c:277 called from poolallocl+0x43 /sys/src/libc/port/pool.c:913
poolallocl(dsize=0x1c, p=0x1c67c) /sys/src/libc/port/pool.c:903 called from poolalloc+0x41 /sys/src/libc/port/pool.c:1043
poolallocl.bsize/ 0x40
poolallocl..safe/ 0x63a9
poolalloc(p=0x1c67c, n=0x1c) /sys/src/libc/port/pool.c:1033 called from malloc+0x1c /sys/src/libc/port/malloc.c:204
poolalloc.v/ 0x3e538
malloc(size=0x14) /sys/src/libc/port/malloc.c:201 called from pingsend+0x1b /sys/src/cmd/ip/gping.c:524
malloc.v/ 0x3e4d0
malloc..safe/ 0xb8f6b1e0
pingsend(m=0x1e994) /sys/src/cmd/ip/gping.c:514 called from main+0x3b5 /sys/src/cmd/ip/gping.c:1091
pingsend.buf/ 0x0
pingsend.ip/ 0x7fffee9c
pingsend.r/ 0x3b9aca00
pingsend..safe/ 0x27b00
pingsend.err/ 0x66b3
main(argv=0x7fffefd0, argc=0x1) /sys/src/cmd/ip/gping.c:1014 called from _main+0x31 /sys/src/libc/386/main9.s:16
main.flags/ 0x0
main.f/ 0x7fffef56
main._argc/ 0x69
main._args/ 0x1d202
main.p/ 0x7fffefe8
main.i/ 0x1
main..safe/ 0x444
main.j/ 0x0
main.v/ 0x23
main.vmax/ 0x64
main.mark/ 0x0
$R
DI 0x7fffef10 SI 0x7fffeed8 BP 0x8
BX 0x3e540 DX 0x40 CX 0xde0b1f6
AX 0xb885e1a2 GS 0x8010001b FS 0x1b
ES 0x1b DS 0x1b TRAP 0xe
ECODE 0x4 PC 0x9cca CS 0x23
EFLAGS 0x10206 SP 0x7fffedb8 SS 0x1b
E0 0xffff0272 E1 0xffff0120 E2 0xffffffff
E3 0x29bc E4 0x35c0023 E5 0x7fffef04
E6 0xffff001b
page fault
/sys/src/libc/port/pool.c:284 treelookupgt+0x18/ MOVL 0x4(CX),AX
reply other threads:[~2001-09-08 23:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.30.0109081929570.3418-100000@athena \
--to=sah@softcardsystems.com \
--cc=9fans@cse.psu.edu \
/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).