Why should I use Asan or any other tool if I already used instrument leaks
(part of XCode), which show the leaks?

On Thu, Feb 1, 2024 at 11:14 PM Jeffrey Walton via curl-library <
curl-library@lists.haxx.se> wrote:

> On Thu, Feb 1, 2024 at 1:57 PM Josh WizardGuy via curl-library
> <curl-library@lists.haxx.se> wrote:
> >
> > Ah my bad. I didn't think it'd be that different with Mac users.
>
> Yeah, I think Valgrind needs to be trained for the M1's. I know
> Valgrind will have to be mindful of the page size on the machine. M1's
> use 16k page size, and that can cause a fair amount of trouble.
>
> I don't see any relevant bug reports for the M1's at the moment:
>
> *
> https://bugs.kde.org/buglist.cgi?bug_status=__open__&content=Apple&product=valgrind
> *
> https://bugs.kde.org/buglist.cgi?bug_status=__open__&content=Silicon&product=valgrind
> *
> https://bugs.kde.org/buglist.cgi?bug_status=__open__&content=M1&product=valgrind
>
> But there does seem to be some chatter:
>
> * https://github.com/LouisBrunner/valgrind-macos/issues/56
> *
> https://github.com/LouisBrunner/valgrind-macos/issues/56#issuecomment-1651811069
>
> You may have to use Asan, Msan and the Leaks Tool until there is first
> class Valgrind support.
>
> Jeff
>
> > On Wed, Jan 31, 2024, 1:29 AM mos via curl-library <
> curl-library@lists.haxx.se> wrote:
> >>
> >> Why to use valgrind? Instruments shows the leaks. Also, if I calls this
> code in a loop, the memory of the process raise for every call,
> >>
> >> > On 31 Jan 2024, at 4:06, Calvin Buckley via curl-library <
> curl-library@lists.haxx.se> wrote:
> >> >
> >> > On Jan 30, 2024, at 6:56 PM, Josh WizardGuy via curl-library <
> curl-library@lists.haxx.se> wrote:
> >> >> Uhhhh. Use valgrind? 🤷
> >> >
> >> > That would be great advice... if Valgrind supported macOS/arm64.
> --
> Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
> Etiquette:   https://curl.se/mail/etiquette.html
>
-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

Reply via email to