On Mon, Feb 5, 2018 at 11:01 AM, enh <e...@google.com> wrote: > On Mon, Feb 5, 2018 at 10:43 AM, Rob Landley <r...@landley.net> wrote: >> On 02/05/2018 11:34 AM, enh wrote: >>> On Sun, Feb 4, 2018 at 6:14 PM, Rob Landley <r...@landley.net> wrote: >>>> For some reason I thought the next release should happen the middle of >>>> this month, but it turns out it was the middle of last month. (Ok, I've >>>> been distracted.) >>>> >>>> So I'm giving myself one more week to tidy up loose ends. I need to fix >>>> ps -T, might get ping ready to promote... >>>> >>>> Anybody want to shout out with something important I forgot? >>> >>> the asan failures in top are being seen more and more often as folks >>> (internal and OEMs) run asan builds on a regular basis. (moore's law >>> ftw!) >> >> This is why I spent so much effort wrangling the NDK, let's see if I can >> reproduce it... > > i don't think you need to. i'm pretty sure i've seen it on the host > too. (the problem, like i said, is that for me it takes a long time to > reproduce by just leaving top running, even though i'm sure that the > crashes that get automatically reported aren't coming from long-lived > top instances.) > > yeah, checking my archive, i see that i reported reproducing this on > the host in the thread surrounding "[PATCH] killall should kill > scripts too".
+agampe who seems to be hitting this more frequently now and can supply a current detailed asan abort... >> error: cannot specify -static with -fsanitize=address. >> >> errorier: cannot run bionic binary on ubuntu host without -static. >> (Sigh, I'll see if I can set up a bionic chroot this evening...) >> >> Rob _______________________________________________ Toybox mailing list Toybox@lists.landley.net http://lists.landley.net/listinfo.cgi/toybox-landley.net