13 - Calling Conventions

Поделиться
HTML-код
  • Опубликовано: 9 фев 2025

Комментарии • 12

  • @tsunderelovers
    @tsunderelovers 11 месяцев назад +2

    Great! super clear explanations and good examples

    • @jstrosch
      @jstrosch  11 месяцев назад +1

      Glad you liked it

  • @wannabe1337
    @wannabe1337 6 месяцев назад +1

    Really Amazing video, it deserves more views. Thanks

    • @jstrosch
      @jstrosch  6 месяцев назад

      Thanks a lot!

  • @reenamola2162
    @reenamola2162 2 года назад +1

    real world decompiled apps for the most part never follow these convention rules. its almost always mixed up in some way or another

    • @jstrosch
      @jstrosch  Год назад

      How so? Most real world apps will be compiled and the compilers follow these conventions. Malware authors or those that use assembly may find it easier to deviate - but even malware authors regularly use standard compilers. Decompilers and disassemblers simply recover what was originally compiled.

  • @majesticdragonfly
    @majesticdragonfly Месяц назад +1

    i hope you resume or update this course :o

  • @ValliNayagamChokkalingam
    @ValliNayagamChokkalingam 2 года назад

    Thank you so much Josh! The calling convention for a particular program is the same for all functions, right? If different calling conventions are used for different functions in the same program, then the program can't be compiled, right?

    • @jstrosch
      @jstrosch  2 года назад +2

      I can’t say for sure as I haven’t looked into it in too much detail. Some compilers let you define the convention, but as to if they enforce that for every function or just programmer written ones I’m not sure. My assumption is that it is the same, that is usually what I see with programs that are not malware. Of course, malware authors or those trying to protect IP may throw all sorts of things at you!

    • @ValliNayagamChokkalingam
      @ValliNayagamChokkalingam 2 года назад

      @@jstrosch Thanks Prof!