cvs commit: src/lib/libc/stdlib malloc.3 malloc.c
dillon at apollo.backplane.com
Sun Feb 12 15:51:19 PST 2006
:I tested Kevin's patch, and I posted a couple of questions/
:possible problems, but never got a response from anyone.
:I assume that no one else has seen any problems using the
:default settings, which is good.
:I'm still wondering about my coredump problem during the
:'configure' phase of building pkgsrc/lang/clisp -- I posted
:about this a day or two ago. The puzzle is complicated by
:comments in 'configure' stating that "this should cause a
:coredump". However, I don't see any coredumps when building
:clisp on NetBSD.
:Any thoughts on this matter? Should I forget about it?
It is testing mprotect() so I assume that the program
explicitly protected the memory and then tried to access
it. A coredump in that case would mean that mprotect()
I have no idea what the difference between NetBSD and DragonFly
is in this case. Maybe DragonFly is generating a different
signal then NetBSD is when the failed access occurs.
<dillon at xxxxxxxxxxxxx>
More information about the Commits