On Sat, Mar 25, 2000 at 12:11:50PM -0800, Jordan K. Hubbard wrote:
> > I did and created malloc.conf as documented there. And things were
> > fine after that. Wouldn't it be better if the build process created
> > a default /etc/malloc.conf ?
>
> It's purely an optional file; one doesn't need to be installed by
> default in order for things to behave as expected. Consider it
> a debugging feature.
You're right. It works for the default case. I was doing an unsupported
operation: experimenting with rfork and the clone() call from Linuxthreads
port.
However, the mere presence of clone() in the same executable
makes malloc unhappy.
8668 test CALL readlink(0x280f1114,0xbfbff7b8,0x3f)
8668 test NAMI "/etc/malloc.conf"
8668 test RET readlink -1 errno 2 No such file or directory
8668 test CALL sigprocmask(0x1,0x28060000,0x28060010)
8668 test RET sigprocmask 0
8668 test CALL sigprocmask(0x3,0x28060010,0)
8668 test RET sigprocmask 0
8668 test PSIG SIGSEGV SIG_DFL
8668 test NAMI "test.core"
The program is:
#include <stdio.h>
#include <unistd.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/wait.h>
main()
{
int status;
pid_t pid;
void *stack;
stack = malloc(4096);
}
It works fine stand alone. But when linked with some other stuff, it core
dumps. If I create /etc/malloc.conf, it's ok.
-Arun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
