Interfaces are great, but they can be a pain to debug. Forgetting one weak link can lead to Access Violation hell. I seem to remember a utility that would let you visualise the links between interfaced objects, but can't remember what it was called. Anybody know?

-
Interfaces are great, but they can be a pain to debug. Forgetting one weak link can lead to Access Violation hell. I seem to remember a utility that would let you visualise the links between interfaced objects, but can't remember what it was called. Anybody know?

Do you have any clever interface debugging tips or tricks?

Comments

  1. Steffen BinasMarch 9, 2015 at 10:20 AM

    There is this: https://github.com/AquaSoftGmbH/RefCountTracer
    It helps you find memoryleaks, but also could show you if a refcount goes below 0.

    ReplyDelete
  2. Lars DybdahlMarch 9, 2015 at 12:20 PM

    Refactor them away :-)
    When the mix of interface reference counting and TObject gets so complex, that the source code is no longer obvious, maintenance costs sometimes become too high and another solution might be better.

    ReplyDelete
  3. Nicholas RingMarch 9, 2015 at 12:36 PM

    Lars Dybdahl Totally agree and it is even worse when reference counting is disabled (like adding an interface reference to an UI component).

    ReplyDelete
  4. Paul ThorntonMarch 9, 2015 at 3:00 PM

    This link was very useful. It also points to a good FastMM tutorial. http://stackoverflow.com/questions/3139344/how-to-find-a-dangling-interface-that-causes-an-av-in-delphi

    ReplyDelete
  5. Jeroen Wiert PluimersMarch 10, 2015 at 12:14 PM

    Paul Thornton and Steffen Binas  thanks (:

    ReplyDelete

Post a Comment