From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d190801292253m2209d289oe0e66692c9c24635@mail.gmail.com>
Date: Wed, 30 Jan 2008 17:53:18 +1100
From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] pico
In-Reply-To: <3845282A-2418-4D61-A7C1-21EEC18BF3C1@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080129224620.59CFA1E8C2B@holo.morphisms.net>
	<3845282A-2418-4D61-A7C1-21EEC18BF3C1@mac.com>
Topicbox-Message-UUID: 3cc7393c-ead3-11e9-9d60-3106f5b1d025

work it out.  it's called debugging.

brucee

On Jan 30, 2008 12:13 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> In this case, it only told me where the program crashed, which told
> me nothing on why (because a different line or a color image worked).
>
>
> On Jan 29, 2008, at 5:46 PM, Russ Cox wrote:
>
> >> 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
> >
>
>