Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 5 Oct 2003 22:06:57 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Marcus =?utf-8?Q?M=C3=BCller?= <znek@mulle-kybernetik.com>
Cc:        znek@freebsd.org
Subject:   Re: Pointer please
Message-ID:  <20031006030656.GK5283@dan.emsphone.com>
In-Reply-To: <27DDB356-F790-11D7-9174-003065838A88@mulle-kybernetik.com>
References:  <27DDB356-F790-11D7-9174-003065838A88@mulle-kybernetik.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 06), Marcus Mller said:
> I'm currently facing a non-trivial problem with the current
> Objective-C runtime on FreeBSD 5.1-CURRENT. The problem popped up
> when trying to create a native port of OGo
> (http://www.opengroupware.org) to FreeBSD.  Specifically, certain
> returned memory should be nil (0), but in fact is 0xd0d0d0d0.

Could be one of two problems.  The program either malloced memory and
tried to use it without zeroing it, or it freed some memory and tried
to keep using it.  In -current, the malloc has the J debugging flag
set, which fills malloced and freed memory with 0xd0 (see the malloc
manpage).

See http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/52907 for a patch
that will let you distinguish freed vs malloced memory, and pinpoint
the exact allocation that's causing you trouble.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031006030656.GK5283>