From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] runtime error
Date: Fri, 3 Jun 2005 14:34:57 +0100 [thread overview]
Message-ID: <e168f43cdd1b0c45441da67d7f347fe4@terzarima.net> (raw)
In-Reply-To: <62144a6c6739b74f077e261c0d742d00@www1.mail.post.cz>
>>mem user overflow
>>hdr 0a110c09 00000020 000076d7 00000000 31514553 faf00030
>>tail 0a110c09 00000020 000076d7 00000000 31514553 faf00030 |
the program has scribbled outside the memory it was allocated
for something on the heap. plan 9's allocator does some checks
that the others might not do, but in any case, allocator
internals differ enough that a slight overrun
might be noticed by one but not another (eg, because
of extra space allocated for alignment)
see malloc(2) and pool(2) for debugging suggestions
such as increasing the checks that are made to allow
it to be caught nearer the actual error.
prev parent reply other threads:[~2005-06-03 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 12:23 pac7
2005-06-03 13:34 ` Charles Forsyth [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=e168f43cdd1b0c45441da67d7f347fe4@terzarima.net \
--to=forsyth@terzarima.net \
--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).