External structure debugging



Hello all,

Any tips for finding what is presumably a problem of too much or too little indirection? I am making progress, but not setting any records. Pointers<g> on safe and effective ways to verify that the addresses are as intended would be appreciated.

High on the suspect list is an external structure with fields for a function pointer and void pointer. It is passed (by address) to a function that gets gets its boxers in a bunch shortly after the call. Interestingly, if I set a breakpoint in the callback (specified by the function pointer), there are side effects that become visible, and their limits _might_ be a clue.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
bills@xxxxxxxxxxxxxxxxxxxx
.



Relevant Pages

  • Re: FastCode RTL Replacement v0.20 Released!
    ... >> Hi John ... >> indirection? ... this does not set up a function pointer or add any level of ... call dword ptr ...
    (borland.public.delphi.language.basm)
  • Re: FastCode RTL Replacement v0.20 Released!
    ... > John O'Harrow wrote: ... >>> indirection? ... this does not set up a function pointer or add any level of ... > call dword ptr ...
    (borland.public.delphi.language.basm)
  • Re: quik popularized by ANSI C
    ... >> dereferencing a function pointer is not exactly meaningful. ... designate the same object with the same number of levels of indirection. ... then 'sizeof fptr' yields the size of the ... As array names do not decay to array pointers, ...
    (comp.lang.c)
  • Re: FastCode RTL Replacement v0.20 Released!
    ... > Hi John ... this does not set up a function pointer or add any level of indirection. ... > library design. ...
    (borland.public.delphi.language.basm)