News for hackers. Stuff that matters.

invalid_name

Re:Reverse engineering the Intel FSP: A Primer on Sunday November 19, 2017 @04:08PM (#15735957)
because the compiler knows that the structure is located exactly 0x1AB bytes before the current function

This should be 0xF bytes before the current function, shouldn't it? I liked it.

Re:Saying Goodbye to Firebug on Tuesday October 24, 2017 @03:54PM (#15544718)
I expected a similar article when it was time to say goodbye to Internet Explorer as well.
Re:Benchmarking shared memory vs message passing on OS X on Wednesday April 05, 2017 @05:16PM (#14045703)
Yes, I got what you meant, and I know that some parts, especially those which cover measuring, should perhaps be investigated deeper. I'll outline the objectives better next time.
Re:Benchmarking shared memory vs message passing on OS X on Wednesday April 05, 2017 @04:06AM (#14040534)
What kind of work would it need sorry? Anyway I can understand this may not seem to be real benchmarking, while writing it eventually became almost an excuse, the very original purpose was to kinda verify my Prof's thesis, whether was really right or not. My intention was not even about to utterly speak about benchmarking nor shared memory (which I both tried to cover though).
Re:Benchmarking shared memory vs message passing on OS X on Tuesday April 04, 2017 @03:42PM (#14036462)
Wanted to just note down the numbers I got by timing, as then I said, I wanted to remark that was interesting how they are being used complementarily and had fun to implement them.
Re:Benchmarking shared memory vs message passing on OS X on Tuesday April 04, 2017 @03:04PM (#14036096)
I haven't even thought about graphs, I just called 'benchmark' the output of time(1).
Re:Benchmarking shared memory vs message passing on OS X on Tuesday April 04, 2017 @03:02PM (#14036085)
Indeed I'm not merely speaking about shared memory, you can find anything anywhere about it. If you had really taken the time to read it, you would have just figured it out.
Re:Dreaming in Reverse Engineering on Friday November 18, 2016 @01:10PM (#12988744)
Mind asking a few things? What's the purpose of this line

  void *call_addr = (void *)CHECKSUM_CALL_ADDR;
to then casting the rvalue to a double void pointer here:

  void **target = (void **)CHECKSUM_CALL_ADDR; 
(why not just void*) ? Also, even though mprotect() succeeds, I got a segfault.
Re:Basic Mach-O binary parser on Thursday November 17, 2016 @04:30AM (#12975857)
Surely I'm gonna look on it :)
Re:Basic Mach-O binary parser on Thursday November 17, 2016 @04:26AM (#12975837)
Yeah, problem is I messed up with links.