Will also print a warning if we detect this condition.
<rdar://problem/45015752>
Created attachment 351607 [details] proposed patch.
Comment on attachment 351607 [details] proposed patch. View in context: https://bugs.webkit.org/attachment.cgi?id=351607&action=review r=me with comment. > Source/JavaScriptCore/runtime/Options.cpp:581 > + && (strstr(asanOptions, "allow_user_segv_handler=1") || strstr(asanOptions, "handle_segv=0")); Do we actually need both or does ASAN work with just allow_user_segv_handler=1?
Comment on attachment 351607 [details] proposed patch. View in context: https://bugs.webkit.org/attachment.cgi?id=351607&action=review >> Source/JavaScriptCore/runtime/Options.cpp:581 >> + && (strstr(asanOptions, "allow_user_segv_handler=1") || strstr(asanOptions, "handle_segv=0")); > > Do we actually need both or does ASAN work with just allow_user_segv_handler=1? We're checking for either here.
Comment on attachment 351607 [details] proposed patch. View in context: https://bugs.webkit.org/attachment.cgi?id=351607&action=review >>> Source/JavaScriptCore/runtime/Options.cpp:581 >>> + && (strstr(asanOptions, "allow_user_segv_handler=1") || strstr(asanOptions, "handle_segv=0")); >> >> Do we actually need both or does ASAN work with just allow_user_segv_handler=1? > > We're checking for either here. Whoops, read that as &&. carry on!
Thanks for the review. Landed in r236839: <http://trac.webkit.org/r236839>.