On Sat, Jun 28, 2008 at 03:37:36PM -0600, Philip Guenther wrote:
On Sat, Jun 28, 2008 at 3:06 PM, Mark B. [EMAIL PROTECTED] wrote:
What is the default value for MALLOC_OPTIONS?
/usr/src/lib/libc/stdlib/malloc.c says NULL, which is suprising, given
that OpenBSD will alert me to memory
What is the default value for MALLOC_OPTIONS?
/usr/src/lib/libc/stdlib/malloc.c says NULL, which is suprising, given
that OpenBSD will alert me to memory issues for programs that
run fine on another BSD.
Also, what options do folks use when they want to really test things
out?
A big thank you
On Sat, Jun 28, 2008 at 3:06 PM, Mark B. [EMAIL PROTECTED] wrote:
What is the default value for MALLOC_OPTIONS?
/usr/src/lib/libc/stdlib/malloc.c says NULL, which is suprising, given
that OpenBSD will alert me to memory issues for programs that
run fine on another BSD.
All the options
On Sat, Jun 28, 2008 at 5:37 PM, Philip Guenther [EMAIL PROTECTED] wrote:
On Sat, Jun 28, 2008 at 3:06 PM, Mark B. [EMAIL PROTECTED] wrote:
What is the default value for MALLOC_OPTIONS?
All the options default to off, with the partial exception of the a/A
option: the default behavior
On Sat, Jun 28, 2008 at 5:32 PM, Mark B. [EMAIL PROTECTED] wrote:
...
So the difference in my case was not malloc options but different
realloc behavior. This lurking disaster worked until I ran it on
OpenBSD:
struct test *tp1, *tp2;
fcn_that_reallocs(tp1);
tp2 = tp1
/usr/src/lib/libc/stdlib/malloc.c says NULL, which is suprising, given
that OpenBSD will alert me to memory issues for programs that
run fine on another BSD.
All the options default to off, with the partial exception of the a/A
option: the default behavior is not quite the same as either
6 matches
Mail list logo
