From: erik quanstrom <quanstro@coraid.com>
To: sretzki@gmx.de, 9fans@cse.psu.edu
Subject: Re: [9fans] memory woes
Date: Fri, 5 Jan 2007 09:54:44 -0500 [thread overview]
Message-ID: <7e4ee9ce78f7ac577e340450c5435773@coraid.com> (raw)
libpool writes a magic byte at the end of the allocation. if this is not present
when memory is free'd, libpool assumes you've corrupted memory and aborts.
- erik
On Fri Jan 5 09:52:13 EST 2007, sretzki@gmx.de wrote:
> > you are forgetting +1 for the null. you need strlen("Hello World")+1.
>
> Heh! Yeah, true. But then the strcpy() would write into non-allocated area, so why does the free()-call make it crash?
next reply other threads:[~2007-01-05 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 14:54 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-05 14:36 sretzki
2007-01-05 14:44 ` erik quanstrom
2007-01-05 14:51 ` sretzki
2007-01-05 14:53 ` Axel Belinfante
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=7e4ee9ce78f7ac577e340450c5435773@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
--cc=sretzki@gmx.de \
/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).