This is so critical to understand thank you for this brilliant breakdown. It really helps when you are very heavy deep into an analysis to understand what is really going on and what values are actually where.
As other comments said, your video has the highest quality among others. I'd love to watch more tutorials of IDA and x64dbg. Reversing the code that is written by yourself and explain the logic was just amazing. Thank you
You are da bomb!!! That feeling when something just clicked inside your head... Now i understand what those are now, you're gonna get another Patreon! Thank you
For the stack cleanup, its adding to the stack pointer, does this mean that the stack pointer will keep increasing? Wont there be a limit to how large the stack pointer's value is? By the way, sorry if my question sounds dumb, but I just dont get that concept.
Not dumb at all! The stack grows negatively so by adding to sp it is actually shrinking the stack back down so it can re-use the previously used space. There are stack limits but in this case we aren't anywhere close to them. There is a pretty good answer on SO about what happens when the stack gets large (stackoverflow.com/questions/15335658/is-there-any-restriction-on-the-maximum-limit-in-usage-of-stack-size).
If this is an OA labs exclusive tutorial how is this available on TH-cam? I know I get more content if I become a patreon member but are some content just offered for free here?
Yeh that's a great question! So we produce these tutorials for our Patreon first (www.patreon.com/oalabs), hence the branding etc. But for specific tutorials we sometimes decide to unlock them for everyone... this usually happens for tutorials that we think can stand on their own (not part of a series) and ones that we think would really benefit a wider audience. This tutorial is actually a good example, an introduction to calling conventions is likely pretty useful for most ppl who are starting out with RE, but for folks who want to go deeper they might be interested in our other 5 tutorials on calling conventions that are Patreon only. I hope that clears it up any confusion, and explains why we have different branding for some videos : ))
C++ is a bit of a beast to RE but __thiscall isn't too crazy @Richard Lyman has the right idea... just need to remember that the class object struct is passed in ECX ... I guess now is a good time to shill for our Patreon haha www.patreon.com/posts/assembly-calling-62676348
I think you are the only TH-camr that teaches reverse engineering this well 👏👏
That's very kind, thank you : )
This is so critical to understand thank you for this brilliant breakdown. It really helps when you are very heavy deep into an analysis to understand what is really going on and what values are actually where.
Hey thanks glad you found this useful : )
@@OALABS always cheers!
As other comments said, your video has the highest quality among others. I'd love to watch more tutorials of IDA and x64dbg. Reversing the code that is written by yourself and explain the logic was just amazing. Thank you
Thanks! We will be exploring debuggers more this month, and of course ... on Patreon : ))
@@OALABS I take donation into account then
I am really appreciated all of your Patreon series. Every single of them is so informative. Thanks a lot!
Thanks : )))
You are da bomb!!! That feeling when something just clicked inside your head... Now i understand what those are now, you're gonna get another Patreon! Thank you
The helpfulness of your channel cannot be overstated. Love it, keep up the great work! 👍🏻
Hey, thanks very much! This is the sort of feedback that keeps us motivated : )
This is one of the most well made videos I've found discussing reversing in general. Well done!
Always coming to your content to brush up the basics really well done
Thank your for sharing! Your content is amazing. Keep up the good work 💪💪
these videos are just insanely good. thank you so much ;-)
thank you!!! amazing work!
Thank you very much ❤️
instantly subscribed and activated the bell lol
Awesome!!!
For the stack cleanup, its adding to the stack pointer, does this mean that the stack pointer will keep increasing? Wont there be a limit to how large the stack pointer's value is? By the way, sorry if my question sounds dumb, but I just dont get that concept.
Not dumb at all! The stack grows negatively so by adding to sp it is actually shrinking the stack back down so it can re-use the previously used space. There are stack limits but in this case we aren't anywhere close to them. There is a pretty good answer on SO about what happens when the stack gets large (stackoverflow.com/questions/15335658/is-there-any-restriction-on-the-maximum-limit-in-usage-of-stack-size).
@@OALABS Thanks for the clarification, I understand better now!
If this is an OA labs exclusive tutorial how is this available on TH-cam? I know I get more content if I become a patreon member but are some content just offered for free here?
Yeh that's a great question! So we produce these tutorials for our Patreon first (www.patreon.com/oalabs), hence the branding etc. But for specific tutorials we sometimes decide to unlock them for everyone... this usually happens for tutorials that we think can stand on their own (not part of a series) and ones that we think would really benefit a wider audience. This tutorial is actually a good example, an introduction to calling conventions is likely pretty useful for most ppl who are starting out with RE, but for folks who want to go deeper they might be interested in our other 5 tutorials on calling conventions that are Patreon only. I hope that clears it up any confusion, and explains why we have different branding for some videos : ))
out of all that call.. one that I hate is the thiscall...
C++ is a bit of a beast to RE but __thiscall isn't too crazy @Richard Lyman has the right idea... just need to remember that the class object struct is passed in ECX ... I guess now is a good time to shill for our Patreon haha www.patreon.com/posts/assembly-calling-62676348