I know that *San are able to do the things they do because of invasive instrumentation, but boy, tools that work without needing special instrumented builds are so much more practical.
-
-
Replying to @TedMielczarek @johnregehr
I'm ok with special instrumented stdlibs, provided the tools make it easy to fetch and use by default (e.g. if Rust's instrumented stdlibs were fetched by rustup -- they can be, but nobody has set that up yet since Rust needs less sanitizing usually)
1 reply 0 retweets 1 like -
The biggest problem here is commercial Android phones. Good luck getting DWARF debug info for any system libs, much less instrumented builds
3 replies 1 retweet 2 likes -
There are docs on how to use ASan on Android, and they start with "do an ASan-enabled build of the entire OS". https://source.android.com/devices/tech/debug/asan …
2 replies 2 retweets 3 likes -
Exactly. Not possible on most consumer devices. This is an *enormous* advantage for iOS. Pity iOS is so closed :(
1 reply 0 retweets 2 likes -
Replying to @pcwalton @TedMielczarek and
Last I checked, Darwin ARM (i.e. iOS) violates the ARM EABI to make it easier to debug by including frame pointers. Good move by Apple.
1 reply 0 retweets 1 like
(Not being sarcastic. Banning frame pointers in the ABI makes life hard for no reason, especially on 64-bit.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.