@rygorous (also, did you just say "approximately zero", as opposed to "zero"?)
-
-
Replying to @cmuratori
@cmuratori I said ~0, i.e. binary-not 0, i.e. 0xffffffff (which is a handful to type).1 reply 0 retweets 0 likes -
Replying to @cmuratori
@rygorous So I have an#if 0 branch here that reads out of thread_typegroup1, so you may well be correct...1 reply 0 retweets 1 like -
-
Replying to @cmuratori
@cmuratori@rygorous You forgot tools to build trace definitions and the mirrored events to avoid admin priv for kernel events..... ugh.1 reply 0 retweets 1 like -
Replying to @voidptr_t
@voidptr_t@rygorous I'm happy to do an update if you can point me to something for the "mirrored events". I don't even know what those are!1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@rygorous Mostly just pointing out endless rat-hole: http://technet.microsoft.com/en-us/library/cc732700.aspx … to http://msdn.microsoft.com/en-us/library/windows/desktop/aa385638(v=vs.85).aspx … To get header from etw...2 replies 0 retweets 1 like -
Replying to @voidptr_t
@voidptr_t@cmuratori Amazingly, Linux independently came up with LTTng which is unfriendly to get data out of in exactly the same ways.2 replies 0 retweets 0 likes -
Replying to @rygorous
@rygorous@voidptr_t@cmuratori Dunno about LTTng, but probably ETW is just a hack job on top of the kernel version...never intended for usr2 replies 0 retweets 0 likes
@shuffle2 @rygorous @voidptr_t ETW is very obviously not a hack job - a _significant_ amount of work went into it. It's just all terrible.
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.