[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#6918) #include statement unsafe

hyc@symas.com writes:
>quanah@zimbra.com wrote:
>> --On Monday, May 02, 2011 12:53 PM +0000 h.b.furuseth@usit.uio.no wrote:
>>> hyc@symas.com writes:
>>>> Nothing in the OpenLDAP code issues a truncate operation of any sort.
>>> There are several fopen(filename, "w") calls, which truncate the file.
>>> Maybe the error confuses slapd so it takes a detour into one of them.
> Irrelevant. In Windows the OS prevents you from writing to an executable file 
> that is currently running. I.e., it is impossible for this to be the cause.

Aha.  OK.  I don't know Windows, so I was reacting to what you said, not
to what you didn't say:-)

> Try it yourself:

Can't without Windows.

> (...)
> If you still believe it's happening inside slapd the obvious thing to do to 
> track this is to run slapd under gdb and set a few breakpoints. E.g., one at 
> the end of the config parser, and one at slapd's call to exit(). At each 
> breakpoint, check the filesize of the slapd.exe.

Something like that was what I had in mind, yes.  I might try anyway.