9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] pool curalloc bug
Date: Mon,  2 Mar 2015 00:06:36 -0800	[thread overview]
Message-ID: <c861fe457b5e52ffd70a12b2e332d67e@brasstown.quanstro.net> (raw)
In-Reply-To: <411f4ed7862275a46cf5a477a3aff0c4@sigma.offblast.org>

On Wed Feb 25 18:40:39 PST 2015, mischief@9.offblast.org wrote:
> does anyone care to take a stab at figuring out why mainmem->curalloc underflows? here's a c program to reproduce.
>

i can't replicate this on amd64/9atom

; 6.curalloc
6.curalloc 786: suicide: sys: trap: fault read addr=0x0 pc=0x202761
acid; stk()
abort()+0x0 /sys/src/libc/9sys/abort.c:6
main(argv=0xfedfff80,argc=0x0)+0x54 /usr/quanstro/curalloc.c:41
_main+0x40 /sys/src/libc/amd64/main9.s:15
; 6c -a curalloc.c>curalloc.acid
; acid -l curalloc.acid 786
/proc/786/text:amd64 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/amd64
acid; (Pool)mainmem
	name	0x00400248
	maxsize	0
	cursize	1072693248
	curfree	16
	curalloc	0			<---
	minarena	0
	quantum	1076101120
	minblock	1852399981
	freeroot	0x00000000
	arenalist	0xfaf0f1fe
	alloc	0x00000000
	merge	0x00000000
	move	0xfedffef8
	flags	32
	nfree	0
	lastcompact	2106590
	lock	0x00000023
	unlock	0x002024de
	print	0x00000025
	panic	0x00201f75
	logstack	0x0000002b
	private	0x002024de

- erik



  parent reply	other threads:[~2015-03-02  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  2:38 mischief
2015-02-26 22:27 ` mischief
2015-03-02  8:06 ` erik quanstrom [this message]
2015-03-02 10:10   ` cinap_lenrek
2015-03-02 10:23   ` 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=c861fe457b5e52ffd70a12b2e332d67e@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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
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).