9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] Fwd: NFS suicide on RPi3 and RPi4 9front, but works on RMiller's Plan9.
Date: Thu, 11 Mar 2021 07:07:24 -0800
Message-ID: <C7223529A8EFDFAECC93267FF826E14C@eigenstate.org> (raw)
In-Reply-To: <10F5F68E-B664-43CF-B4F6-E2318B5BEC80@gmail.com>

Quoth Shiro <rt9f.3141@gmail.com>:
> Hello,
> 
> I’m not sure I’m reporting to the appropriate place.  Please advise.  And apologies in advance if I’m spamming this group.
> 

This is fine, but 9front@9front.org is probably
better for 9front specific questions.

As far as uploading information -- 9front ships
with webpaste, so it's easy to get text uploaded,
which would let people copy values.

> Photo 3: acid is pointing to line 431.  From above, n is too large
> to be a strlen.  I suspect it actually failed in memmove(), but
> I’m not sure — I’ve only got 2 months on Plan9/9front and this is
> the first time I do acid.

Acid just shows whole words, so you're seeing 64
bits of a 32 bit value.  If you look closely,
you'll actually notice that the top bits in 'n'
are also the bottom bits of 'dat'

It's a bit unfortunate, you either have to tell
acid how to format the type, or you have to know
that you just need to ignore the top bits.

Anyawys, the faulting address is

        addr=0x100061fa0 pc=37930

Which shows up in R4. Given that *almost* the same
addresses (0x61fa0) in the other registers.  It
looks like it could be stack corruption.

Is this easy to reproduce?  Are you using the
binary from the last release, or is it your own
build?


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T995ec2230d16bd0b-M13cd1034eae8ce315d7a78eb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-03-11 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FE4D07EC-A08F-454D-B1EA-A81B4AD88B84@gmail.com>
2021-03-10 20:14 ` Shiro
2021-03-11 15:07   ` ori [this message]
2021-03-24 23:18     ` [9fans] " Shiro
2021-03-29 15:19       ` cinap_lenrek

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=C7223529A8EFDFAECC93267FF826E14C@eigenstate.org \
    --to=ori@eigenstate.org \
    --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

9fans - fans of the OS Plan 9 from Bell Labs

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.vuxu.org/9fans

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 9fans 9fans/ https://inbox.vuxu.org/9fans \
		9fans@9fans.net
	public-inbox-index 9fans

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.9fans


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git