[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: allocate_string_data memory corruption

From: Ken Raeburn
Subject: Re: allocate_string_data memory corruption
Date: Wed, 18 Jan 2006 22:21:09 -0500

On Jan 18, 2006, at 20:15, Stefan Monnier wrote:
If you use eassert instead of "if (...) abort();" you won't have to worry about it because the line number is embedded in the error message, so you
don't even need debug-symbols.
OTOH you need to compile with -DENABLE_CHECKING.

BTW, a configure option to turn on ENABLE_CHECKING is pretty trivial, I'll check it in if people want it... I assumed it wouldn't be of general enough interest, but we have --enable-asserts for the XASSERTS code... maybe we should have one configure option turn on both?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]