[Samba] Problem with MS Visual SourceSafe and samba V3.0.14anb1

[Scott R. Burns]

I am not sure. Is this a compile time version of the function that I have to
opt to use in the samba source ? I am running precompiled binaries from the
NetBSD site.

The malloc implementation appears to have a couple of debug options with a
ton of flags you can pass in:

ENVIRONMENT
     The following environment variables affect the execution of the alloca-
     tion functions:

     MALLOC_OPTIONS
          If the environment variable MALLOC_OPTIONS is set, the characters
it
          contains will be interpreted as flags to the allocation functions.

FILES
     /etc/malloc.conf  symbolic link to filename containing option flags

EXAMPLES
     To set a systemwide reduction of cache size, and to dump core whenever
a
     problem occurs:

           ln -s 'A<' /etc/malloc.conf

     To specify in the source that a program does no return value checking
on
     calls to these functions:

           extern char *malloc_options;
           malloc_options = "X";

Is this what you are looking for ?

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-----Original Message-----
From: Jeremy Allison [mailto:jra at samba.org]
Sent: Thursday, October 13, 2005 7:57 PM
To: Scott R. Burns
Cc: samba at samba.org
Subject: Re: [Samba] Problem with MS Visual SourceSafe and samba
V3.0.14anb1


On Thu, Oct 13, 2005 at 01:55:29PM -0400, Scott R. Burns wrote:
> I have upgraded my samba on a NetBSD/i386 V2.0.2. I was previously at
> V3.0.10nb2 and I am now at: V3.0.14anb1. My developers are starting to
> report problems when checking source code in and out of VisualSource Safe.
> Most users are W2K SP4 or WXP SP1a or SP2. Problem has been reported by
both
> XP and W2K users.
>
> The problems reported in the samba log file are thousands of:
>
> [2005/10/11 16:07:05, 0] lib/util.c:Realloc(971)
>   Memory allocation error: failed to expand to 4896 bytes
> [2005/10/11 16:07:05, 0] lib/util.c:Realloc(971)
>   Memory allocation error: failed to expand to 4896 bytes
> [2005/10/11 16:07:05, 0] lib/util.c:Realloc(971)
>   Memory allocation error: failed to expand to 4896 bytes
>
>
> The 4896 value is quite common, but it does vary to other values in the 4K
> range.
>
> I have observed a couple of other reports about Realloc() failing on the
net
> but nothing specific. Does anyone know if a specific release fixes this
> before I attempt to revert backwards ?

Realloc failures are bad.... Looks like a process is running out
of memory. Does *BSD have malloc_check_ ?

Jeremy.