Mario Sergio Fujikawa Ferreira wrote:
>
> Besides, a failing malloc should return NULL, shouldn't
> it? I would have expected core if I had malloc_options="X" which
> I do not (in fact, I have no malloc_options).
IF the malloc fails, it should return NULL. But this only happens in the
ca
Daniel,
On Sun, Jul 23, 2000 at 12:01:53AM +0900, Daniel C. Sobral wrote:
> Mario Sergio Fujikawa Ferreira wrote:
> >
> > Backtracing showed that the problem was due
> > to the malloc function inside the get_mem function.
> > get_mem() is used to find out the largest possible memory segm
Mario Sergio Fujikawa Ferreira wrote:
>
> Backtracing showed that the problem was due
> to the malloc function inside the get_mem function.
> get_mem() is used to find out the largest possible memory segment.
> It incrementaly reduces the segment passed to malloc to alloc.
> It is
Hi,
I just added sysutils/memtest to the FreeBSD ports tree a
couple of days ago. It is a utility to test for faulty memory
subsystem.
However, I've been having some problems with it.
They are not fatal, but really annoying. I am in contact with
the author to try working them out.
4 matches
Mail list logo
