Re: [webkit-dev] Why does RELEASE_ASSERT not have an error message?

2017-02-23 Thread Filip Pizlo
Geoff, If you find a case of code that looks like this: if (!things) { dataLog(...); RELEASE_ASSERT_NOT_REACHED(); } and this code blames to fpi...@apple.com, then I can tell you why I wrote it that way. It was because I had crashed on some assert in that function, and I needed to figur

Re: [webkit-dev] Why does RELEASE_ASSERT not have an error message?

2017-02-23 Thread Geoffrey Garen
> On Feb 22, 2017, at 12:16 PM, Filip Pizlo wrote: > > >> On Feb 22, 2017, at 11:58 AM, Geoffrey Garen wrote: >> >> I’ve lost countless hours to investigating CrashTracers that would have been >> easy to solve if I had access to register state. > > The current RELEASE_ASSERT means that ever

Re: [webkit-dev] Why does RELEASE_ASSERT not have an error message?

2017-02-23 Thread Mark Lam
To give an update: I plan to experiment and get some size and perf numbers and report back later. But since this is not a high priority task for me, it may be a while before I get back to this. Mark > On Feb 22, 2017, at 1:25 PM, Ryosuke Niwa wrote: > > On Wed, Feb 22, 2017 at 12:41 PM, Mark

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

2017-02-23 Thread Jacob Greenfield
In that case, I agree that it does not make much sense to implement the FIDO U2F API. I would definitely be interested in working on Web Authentication for WebKit. Rick - I think collaborating with people working on Chromium and Edge would be great. Thanks! - Jacob Greenfield > On Feb 22, 20