I'll try that tonight on the FreeBSD system. We have these options for
malloc:
A All warnings (except for the warning about unknown flags being
set) become fatal. The process will call abort(3) in these
cases.
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.
> We have a report in Bugzilla (#464), concerning twm. This test can
> only be made on NetBSD:
>
> =======================================================
> if you set /etc/malloc.conf to "AJ" (fill malloc'ed region with random
> value),
> twm crashes occasionary. i'm yet to find out a concrete way to repeat the
> symptom, however, it seems that twm (or some library) is touching
> malloc'ed memory region without initialization.
> =======================================================
>
> Could somebody with NetBSD please try to reproduce this?
> I'd at least need a debugger backtrace to get a clue where the
> problem may be.
--
Alexander Pohoyda
<[EMAIL PROTECTED]>
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
