jmason at rim.com
Thu Dec 16 10:09:14 PST 2010
> -----Original Message-----
> From: webkit-dev-bounces at lists.webkit.org [mailto:webkit-dev-
> bounces at lists.webkit.org] On Behalf Of Samuel Rivas
> Sent: Thursday, December 16, 2010 3:03 AM
> To: Zoltan Herczeg
> Cc: webkit-dev Development
> On 6 December 2010 22:31, Zoltan Herczeg <zherczeg at inf.u-szeged.hu>
> > Crash in WTF::fastMalloc? Such things only happen if something
> > memory areas belongs to the memory manager (i.e overwrites some bytes
> > before or after a block returned by malloc). Try some valgrind
> > on mac to detect those writings into "red zones".
> How can you use valgrind to help on that? We had some symptoms similar
> to this and also came to the conclusion that probably something is
> overwriting the structures used by fast malloc, but couldn't find
> anything with valgrind. Overwriting in an area that has bee reserved
> is not an error vangrind finds, at least not with any options that I
It is possible to add macros to the code to help valgrind know which areas are being used by a custom allocator. (See VALGRIND_MALLOCLIKE_BLOCK and VALGRIND_FREELIKE_BLOCK, for example.) I'm not sure if they're useful in this situation, but they're worth taking a look at.
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
More information about the webkit-dev