Hi guys .

Hi guys .
I had just finished implementing the new version of delphi detours library (v2).
This new version was born from the scratch , and it's the same thing for InstDecode library.

Many BugFix and new hooking architecture was introduced allowing support for multi hooks !
Whatever your hook was installed from your app process or via (dll,..).DDL v2 will manage your hook to run without problems .

Beyond the multi hooks support, there are many new features :
-VEX support .
-Instructions Maping.
-Hooking interfaces methods.
-New function to detect if a function was hooked.
-Three bytes escape table support.
-I will try to cover the rest later.

Before publishing the new version i need some beta tester to test the new version.

If you want receive a beta version ..send me a mail to:
ismspider at gmail.com

https://code.google.com/p/delphi-detours-library/
https://code.google.com/p/delphi-detours-library

Comments

  1. This sounds fantastic! Could you expand on multi-hook support, please? It's a particular interest of mine (because many IDE plugins from many people all hook the same function in the IDE, currently it has to be done very carefully.)

    ReplyDelete
  2. Panagiotis Drivilas 
     IAT & EAT are supported , however DDL does not patch the tables . 
    DDL hook at the top of original functions implementation .

    ReplyDelete
  3. Then those are not IAT/EAT hooks by definition :)

    ReplyDelete
  4. Mahdi Safsafi, is it in the same project on Google Code? The SVN commit log doesn't show any source changes since July (some wiki changes in August, that's it.)  https://code.google.com/p/delphi-detours-library/source/list

    Am I looking in the wrong place?

    ReplyDelete
  5. David Millington Currently , it's beta .
    As i mentioned , it's only available for beta tester.
    if you want to receive a beta version let me know.

    ReplyDelete
  6. Mahdi Safsafi Sorry. I didn't make the connection, just not thinking. Will send you an email.

    ReplyDelete
  7. Mahdi Safsafi Why not do beta publicly for something that is open source anyway? That is usually what branches are for.

    ReplyDelete
  8. Stefan Glienke At least to avoid duplicated bugs .

    ReplyDelete
  9. Stefan Glienke Reporting same bugs twice.

    ReplyDelete
  10. I still don't get it.
    A public test with using an issue tracker makes it less likely that you get duplicates because people are not just emailing you the issues not knowing what others might have found. Also usually you get way better feedback because others can contribute to found bugs and add more information.

    ReplyDelete
  11. Stefan Glienke I usually send my app to a limit number of friends.
    They report bugs , and give their opinions.
    And finally i introduce my beta app for public.

    ReplyDelete

Post a Comment