[webkit-dev] Debugging Memory Errors

[Michelangelo De Simone]

Doesn't "debug-safari --debug --guard-malloc" make the trick?

If you need to target the web-process - as I think - you may also want to append "--target-web-process".
-- 
Bye,
Michelangelo

On May 15, 2013, at 5:54 PM, Bear Travis <betravis at adobe.com> wrote:

> Hi WebKit,
> 
> I was wondering how folks debug memory errors such as use after free and allocated memory overflows.
> I have seen some bugs mentioning libgmalloc.
> 
> I can run safari with:
> run-safari --debug --guard-malloc
> But I don't seem to get the full stack traces I have seen in the bugs.
> 
> I have also seen mention of setting DYLD_INSERT_LIBRARIES to /usr/lib/libgmalloc.dylib, but doing so seems to lock up the build-webkit command.
> 
> Any tips/tricks/pointers would be greatly appreciated,
> -Bear
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev