From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] panic: D2B called on non-block 8067a168 (double-free?)
Date: Wed, 30 Apr 2003 18:27:31 -0400 [thread overview]
Message-ID: <d8962225703bc31de993ba376da7e5ba@plan9.bell-labs.com> (raw)
In-Reply-To: <200304302219.h3UMJwx05738@zamenhof.cs.utwente.nl>
That's discouraging. Let us know if it happens again.
It looks like there's a ref count bug on some hardly
ever used path.
prev parent reply other threads:[~2003-04-30 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 22:19 Axel Belinfante
2003-04-30 22:27 ` rsc [this message]
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=d8962225703bc31de993ba376da7e5ba@plan9.bell-labs.com \
--to=rsc@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).