From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pico
Date: Tue, 29 Jan 2008 17:46:24 -0500 [thread overview]
Message-ID: <20080129224620.59CFA1E8C2B@holo.morphisms.net> (raw)
In-Reply-To: <DA9E4326-C4FC-40B5-B4AF-D8E3F7468C2F@mac.com>
> I get something that ends in "(double-free?)" and then the program
> crashes, but something like
This usually means you have freed the same pointer twice
or you are passing a pointer to free that was not returned
by malloc. If you run acid to get a stack trace to see the
context of the free, that is often enough to identify the
problem.
% acid pid
acid: stk()
...
^D
%
Russ
next prev parent reply other threads:[~2008-01-29 22:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:05 [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-26 14:05 ` Russ Cox
2008-01-26 14:09 ` Pietro Gagliardi
2008-01-26 14:55 ` Russ Cox
2008-01-26 23:22 ` Pietro Gagliardi
2008-01-27 18:05 ` Skip Tavakkolian
2008-01-27 18:55 ` Pietro Gagliardi
2008-01-27 19:29 ` [9fans] pico Steve Simon
2008-01-28 23:36 ` Russ Cox
2008-01-29 0:30 ` Pietro Gagliardi
2008-01-29 5:30 ` Bruce Ellis
2008-01-29 20:33 ` Pietro Gagliardi
2008-01-29 20:35 ` Pietro Gagliardi
2008-01-29 22:46 ` Russ Cox [this message]
2008-01-30 1:13 ` Pietro Gagliardi
2008-01-30 6:53 ` Bruce Ellis
2008-01-30 23:42 ` Pietro Gagliardi
2008-01-30 23:55 ` Pietro Gagliardi
2008-01-31 7:41 ` Bruce Ellis
2008-02-05 3:01 ` Pietro Gagliardi
2008-01-27 19:14 ` [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-27 23:44 ` Pietro Gagliardi
2008-01-28 0:18 ` Pietro Gagliardi
2008-01-28 1:08 ` Pietro Gagliardi
2008-01-28 1:22 ` erik quanstrom
2008-01-28 3:23 ` Pietro Gagliardi
2008-01-28 9:24 ` mattmobile
2008-01-28 16:20 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 23:06 [9fans] pico Fariborz (Skip) Tavakkolian
2002-07-17 21:57 ` Sam
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=20080129224620.59CFA1E8C2B@holo.morphisms.net \
--to=rsc@swtch.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).