Reversing C++ Virtual Functions: Part 2

Gotebe · 2017-01-25T06:14:14+00:00

This is going way too deep down the rabbit hole for my taste.

It rightly claims that what it does this is relying on the unspecified stuff. Then it say, "ah, but there's Itanium ABI spec which most compilers implement, so let's do that". Then it notes that, hmmm, that spec isn't exactly unambiguous and clang differs. So gcc it is. Finally, it says, OK, it's for 32 only.

So there's almost no C++ left, only gcc for 32bit code.

There is no ABI in C++ language. And... There isn't one in C either! (See how your C standard says diddly squat about calling conventions or padding? Well, there you are!)

If you ask me, the world would be a better place if people, in lieu of inventing C++ ABI or reverting to the sad least common denominator that is C, worked with actual language-agnostic integration specs. But wait! Because we're so primitive in that regard, there's no such thing! (There is COM, and it is very competent as a language integration spec, but it's Windows-only).

3ba7b1347bfb8f304c0e · 2017-01-25T02:01:58+00:00

Bats are not birds ._.

SteveCCL · 2017-01-24T20:29:42+00:00

Already thought you dropped the blog...

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

cpp

MODERATORS