Re: @cmuratori's "The Worst API Ever Made" http://mollyrocket.com/casey/stream_0029.html … "Mercifully, [processing events] is just a bunch of structure accesses"...
-
-
Replying to @rygorous
@cmuratori ...OR IS IT? Ladies and gentlemen, feast your eyes on this: http://msdn.microsoft.com/en-us/library/windows/desktop/aa382754%28v=vs.85%29.aspx …1 reply 0 retweets 2 likes -
Replying to @rygorous
@cmuratori Far from a simple struct access; there's another entire API just to get data out of these things. http://msdn.microsoft.com/en-us/library/windows/desktop/aa964843%28v=vs.85%29.aspx … etc.1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori FWIW, that code you posted? That's nowhere close to working. E.g. your "ThreadID" is always ~0.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@rygorous (also, did you just say "approximately zero", as opposed to "zero"?)1 reply 0 retweets 0 likes -
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
@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 - Show replies
New conversation -
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.