9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ip/rarpd problem
Date: Tue,  3 Sep 2002 20:35:11 -0400	[thread overview]
Message-ID: <3d3b860ed7fac9e8c6f365d964fdec38@plan9.bell-labs.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Given where it crashes, it isn't garbled, 0xffff0000 is what is being passed.
One possibility is that something on the stack above _fmtdispatch trashed the
stack.  I don't see anything obviously wrong.  We stopped running rarpd when
our last sun went nova.  You might try rebuilding the libraries and rarpd and
see if it still happens.  The line numbers from your acid stack dump are
a bit different than the current source, so you might have some incompatible
changes in there (or acid is guessing badly).

Otherwise, keep digging, bug snprint and see if fmt is 0xffff0000 coming in,
etc.  If it's consistently repeatable, it should be easy to track down just
by marching tests through the code.

[-- Attachment #2: Type: message/rfc822, Size: 3024 bytes --]

From: kazumi iwane <kiwane@mx6.ttcn.ne.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] ip/rarpd problem
Date: Wed, 04 Sep 2002 07:10:53 +0900
Message-ID: <20020903221016.ZHGO17976.mta5p@isabella>

ip/rarpd dies as soon as it receives a request.

 rarpd 208: suicide: sys: trap: fault read addr=0xffff0000 pc=0x00002c19

Below is what acid tells me. dofmt:fmt looks bad. This should be equal
to efmt$1, a static format string defined in eipfmt(). I can't figure
out why this looks garbled.

Can somebody please enlighten me?

acid: stk()
At pc:0x00002c19:dofmt+0x138 /sys/src/libc/fmt/dofmt.c:37
dofmt(*dofmt:fmt=0xffff0000,*dofmt:f=0x7fffe4a8)
	called from vsnprint+0x62 /sys/src/libc/fmt/vsnprint.c:20
vsnprint(*vsnprint:len=0x00000028,*vsnprint:buf=0x7fffe55c,
         *vsnprint:args=0x7fffe50c,*vsnprint:fmt=0xffff0000)
	called from snprint+0x2b /sys/src/libc/fmt/snprint.c:13
snprint(*snprint:fmt=0xffff0000,*snprint:buf=0x7fffe55c,
        *snprint:len=0x00000028)
	called from eipfmt+0x272 /sys/src/libip/eipfmt.c:38
eipfmt(*eipfmt:f=0x7fffe5f0)
	called from _fmtdispatch+0x94 /sys/src/libc/fmt/fmt.c:187
_fmtdispatch(*_fmtdispatch:isrunes=0x00000000,*_fmtdispatch:f=0x7fffe5f0,
             *_fmtdispatch:fmt=0x000114b8)
	called from dofmt+0x75 /sys/src/libc/fmt/dofmt.c:62
dofmt(*dofmt:fmt=0x000114b6,*dofmt:f=0x7fffe5f0)
	called from vsnprint+0x62 /sys/src/libc/fmt/vsnprint.c:20
vsnprint(*vsnprint:len=0x00010000,*vsnprint:buf=0x7fffe744,
         *vsnprint:args=0x7fffe650,*vsnprint:fmt=0x000114b6)
	called from sprint+0x2c /sys/src/libc/fmt/sprint.c:13
sprint(*sprint:fmt=0x000114b6,*sprint:buf=0x7fffe744)
	called from main+0x330 /sys/src/cmd/ip/rarpd.c:141
main(*main:argv=0x7fffefe4,*main:argc=0x00000000)
	called from _main+0x31 /sys/src/libc/386/main9.s:16

-- kazumi iwane

             reply	other threads:[~2002-09-04  0:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04  0:35 presotto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-08 18:35 presotto
2002-09-04 12:26 presotto
2002-09-05 22:18 ` kazumi iwane
2002-09-08 18:31   ` kazumi iwane
2002-09-04  8:42 Charles Forsyth
2002-09-03 22:10 kazumi iwane

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=3d3b860ed7fac9e8c6f365d964fdec38@plan9.bell-labs.com \
    --to=presotto@plan9.bell-labs.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).