9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] stats(1) suicide
Date: Sat, 9 Aug 2014 00:57:37 +0200	[thread overview]
Message-ID: <2ab318cd6a5d404f651e57691a1ac5ad@felloff.net> (raw)
In-Reply-To: <A60F3A79-73DF-4197-AADD-A09EC6DC7185@ar.aichi-u.ac.jp>

kenji,

the note bug should not apply to release 9front-3730.5d864bfef728.iso.bz2,
as it was introduced in a later commit. also, cwfs doesnt install any note
handlers so it cant be affected.

> cwfs64x 319: suicide: invalid address 0x1056efee8/16384 in syscall pc=0x22ac56
> cwfs64x 319: suicide: sys: bad address in syscall pc=0x22ac56

i looked up the pc addresses and it tells me this is the sleep syscall. this
is very odd. sl and others run cwfs64x just fine on the latest pc64 and i'v
not seen such an issue yet.

can you verify by running:

acid /amd64/bin/cwfs64x
src(0x22ac56)
asm(sleep)

the last line will will disassemble the sleep syscall stub, and should
result in something like:

acid: asm(sleep)
sleep 0x000000000022ac53	MOVQ	BP,a0+0x0(FP)
sleep+0x5 0x000000000022ac58	MOVQ	$0x11,BP
sleep+0xc 0x000000000022ac5f	SYSCALL
sleep+0xe 0x000000000022ac61	RET

--
cinap


  reply	other threads:[~2014-08-08 22:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07  2:51 sl
2014-08-07 11:56 ` [9front] " cinap_lenrek
2014-08-08  7:45   ` arisawa
2014-08-08 16:01     ` sl
2014-08-08 21:30       ` arisawa
2014-08-08 21:44         ` sl
2014-08-08 22:35           ` arisawa
2014-08-08 22:57             ` cinap_lenrek [this message]
2014-08-09  6:05               ` arisawa
2014-08-09 15:42                 ` cinap_lenrek
2014-08-09 22:46                   ` arisawa

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=2ab318cd6a5d404f651e57691a1ac5ad@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /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).