ImagehlpApiVersion

Hello,
I was looking at the ImagehlpApiVersion function to see if there was
an easy way to catch the common problem with using the dbghelp.dll
shipped with the OS rather than the one in debugging tools.

However, both the DbgHelp.dll files report version 4.0.5 ....

Is this a 'feature' or have I misunderstood the purpose of this and
the ImagehlpApiVersionEx API?

Regards,

Hello Roger.

ImagehlpApiVersion is something that carries over from the old days before the 
existence of dbghelp.dll.  The function is completely irrelevant to your 
needs.

I have always suggested if you need a certain version dbghelp.dll to support 
your application, then you should ship with it in your program directory and 
specifically load it from there.  That is how windbg.exe and the other 
debuggers load dbghelp.dll and that is also how dbghelp.dll loads symsrv.dll 
and srcsrv.dll.  All three of these modules are completely redistributable. 
You own your destiny here.

.p

<roger.orr@gmail.com> wrote in message 
news:eadc2578-dbff-43aa-8aba-39db61d044a0@e25g2000prg.googlegroups.com...
Hello,
I was looking at the ImagehlpApiVersion function to see if there was
an easy way to catch the common problem with using the dbghelp.dll
shipped with the OS rather than the one in debugging tools.

However, both the DbgHelp.dll files report version 4.0.5 ....

Is this a 'feature' or have I misunderstood the purpose of this and
the ImagehlpApiVersionEx API?

Regards,
Roger. 

On Mar 14, 5:59 pm, "Pat Styles [MSFT]"
<pat.sty...@microsoft.com>
wrote:
> Hello Roger.
>
> ImagehlpApiVersion is something that carries over from the old days before
the
> existence of dbghelp.dll.  The function is completely irrelevant to your
> needs.

Fair enough -- it was looking that way :-)

> I have always suggested if you need a certain version dbghelp.dll to
support
> your application, then you should ship with it in your program directory
and
> specifically load it from there.

My problem is with little debug tools that are implemented as a DLL.
I don't want to install dbghelp.dll in the host process directory.

My current solution is to copy the debugging tools version of
dbghelp.dll
as dbgcopy.dll and load that DLL in my tools.

Regards,