Re: Finally have cleared the leaks ...

On Tue, 24 Mar 2020, 10bxjfhf wrote:
>
> and MAGICK_HOME => to the executable directory with all of the DLLs etc, then 
> I call again:
>
> InitializeMagick( static_cast<const char*>( wsExePath) );
>
> and I again trace the log events.
>
> 8 go to stderr and the next 10 or so go to the text log file.
>
> Since I did not specify a path they end up in the parent of my debug 
> directory - by now I know where to look :-)
>
> After this I try to set the new log file & path, but it does nothing and 
> won't do anything until a new log file needs to be created because just 
> assigning a new name & path does not close the current file.
>
> Trying to set the log file path & name before the second call to 
> InitializeMagick() does not cause any errors but also does nothing because 
> the default is reset when Initialize.. gets called the second time.

Remember that the new SetLogDefault APIs are writing into a static 
storage location so they will not be influenced by InitializeMagick(). 
When InitializeMagick() is called, logging is initialized and the 
static default values should be used.  The static default values are 
only used during initialization.

> Still not familiar enough with Hg to be able to just update via a 'pull' - 
> being a non-command-line guy I am using TortoiseHg but it look quite 
> different from TortoiseGit :-(

Normally one does a "synchronize", also known as "pull" (which updates 
the repository itself) followed by an "update", which attempts to 
update the working files with changes.  If you are lucky you will not 
need to do a merge.

TortoiseHG provides the option to automatically update when doing the 
"synchronize".

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt