You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I am starting to wonder... can anybody at all do a syscall::NtCreateFile:entry probe in dtrace that print the filename attempted opened without getting "dtrace: processing aborted: Illegal byte sequence" within the first minute. If you can- i would love to see how
If first print printf("%c%c...",((struct ustr*)this->fname)->buffer[0],((struct ustr*)this->fname)->buffer[1]...) sometimes it starts working untill next reboot. It just seems so arbitrary and non deterministic. Either there is something I dont know or dtrace is buggy
when it fails it because the printf statement will always continue to the first 0x0000 when printing wide strings, and if meets invalid char it fails- even if not going to print it.
ive spent more then 100 hours trying to print that.... i am starting to think its easier to find a way to disable patchguard and do old syscall hooking
Quizás nada que ver con tu tweet pero yo no puedo jugar con máquinas virtuales (@virtualbox) mientras estoy en safeMode en W10, sí NtCreateFile esta tratando de decirme algo que no comprendo... Fuck 
.pic.twitter.com/SNNC2JnAbz
Just a random guess: can it be that it does not handle FILE_OPEN_BY_FILE_ID correctly and tries to interpret its binary input as a string?
Ive also thought about that- but it fails with somethng beginning with {146F1A80-4791-11D0-A5D6-28DB04C10000}
if(((struct ustr*)this->fname)->buffer[ ((*this->len)/2)-1 ] < 255 ) { if(((struct ustr*)this->fname)->buffer[ ((*this->len)/2) ] == 0) { printf("%ws", ((struct ustr*) this->fname)->buffer ); } works
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
