Date: Tue, 28 Aug 2001 12:19:56 -0500 From: "Steven Ames" <steve@virtual-voodoo.com> To: "Andrew Gallatin" <gallatin@cs.duke.edu> Cc: "David O'Brien" <obrien@FreeBSD.ORG>, "Jim Bryant" <kc5vdj@yahoo.com>, <FreeBSD-hackers@FreeBSD.ORG> Subject: Re: TCSH bug... Message-ID: <00e101c12fe5$a95bda70$28d90c42@eservoffice.com> References: <3B8AC157.5000203@yahoo.com><020701c12f43$8e0e2310$28d90c42@eservoffice.com><3B8AC8DB.5090603@yahoo.com><004801c12f49$66cccb20$28d90c42@eservoffice.com><20010827201407.A32152@virtual-voodoo.com><3B8B05AF.9070004@yahoo.com><20010827200243.A8113@dragon.nuxi.com><20010828092016.B21396@virtual-voodoo.com> <15243.50114.846473.519938@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Andrew Gallatin" <gallatin@cs.duke.edu>
> Actually, it is a tcsh bug. Try playing with the MALLOC_OPTIONS
> env. variable in -stable. Specifically, set it to 'AJ' & I bet it will
> drop core in -stable. Eg:
> [EXAMPLE DELETED]
> Note that -current has malloc options 'AJ' on by default to catch just
> this kind of bug.
Ah. That wasn't clear from 'man malloc' under CURRENT. Setting
MALLOC_OPTIONS = "J" (on -STABLE) causes the dump. Now
according to the man page for malloc:
J Each byte of new memory allocated by malloc(), realloc() or
reallocf() as well as all memory returned by free(), realloc()
or
reallocf() will be initialized to 0xd0. This options also sets
the ``R'' option. This is intended for debugging and will
impact
performance negatively.
This option is used to catch places where the code makes assumptions
about the contents of malloc memory? (e.g. that it is zeroed)?
I will submit a problem report to Christos but I want to make sure
that I can explain exactly what is happening and why...
-Steve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00e101c12fe5$a95bda70$28d90c42>