Page 1 of 1


PostPosted: Tue Jan 29, 2019 9:49 am
by Han312
We are using HideLeak( unit|function ) to hide specific leak messages (unit from an external)

This worked till now fine.
Now we updated to the newest libraries and have the problem that all functions have random names.
And we get hundreds of leaks reported.

Does HideLeak( unit ) hide all leaks from that unit?

It seems to work, but it is not mentioned in the help

But one exception we cannot hide:

allocation number: 22002470
program up time: 55,83 s
type: Mutex Handle
handle: $b44
access rights: $1f0001
name: \BaseNamedObjects\SafeNet-SentinelSMEMINIT

main thread ($11b0):
671a915e madExcept32.dll madExceptDbg 3770 CreateMutexACallback
0041baba abc.exe Winapi.Windows CreateMutexA

Code: Select all
HideLeak ( 'WinApi.Windows|CreateMutexA' )
does not seem to work.
How can we ignore (hide) that leak?

Code: Select all
HideLeak ( 'Windows|CreateMutexA' )


Re: HideLeak

PostPosted: Tue Jan 29, 2019 10:14 am
by madshi
Hiding all leaks of one unit by using "HideLeak(unit)" is (I think) not something I intended to support, but if it works fine, I see no problem with using it... :D