Quoth Shiro <rt9f.3...@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 9fr...@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
