Hi folks

Last week I was happily debugging my C DLL tcl extension using Visual
Studio. Today tclsh85 refuses to load the extension generating an
alert dialog quoting an R6034 run-time error. If I recompile the
extension as a Release rather than Debug I can load and use the DLL as
normal. I'm mystified.

Has anyone else encountered this (it seems to do with M$ manifest
files) and can suggest a way forward? Tomorrow, I plan to rebuild Tcl/
Tk etc from source with Debug on (I am currently using ActiveTcl
8.5.8) and see if that helps - I really do need to debug my extension :
( Not sure if this will help as it all worked on Friday!!! I am
suspicious that the M$ Debug run-time libraries are not being
found....


kind regards
Julian

στις 7/6/2010 19:27, O/H JHJL έγραψε:
> Hi folks
>
> Last week I was happily debugging my C DLL tcl extension using Visual
> Studio. Today tclsh85 refuses to load the extension generating an
> alert dialog quoting an R6034 run-time error. If I recompile the
> extension as a Release rather than Debug I can load and use the DLL as
> normal. I'm mystified.
>
> Has anyone else encountered this (it seems to do with M$ manifest
> files) and can suggest a way forward? Tomorrow, I plan to rebuild Tcl/
> Tk etc from source with Debug on (I am currently using ActiveTcl
> 8.5.8) and see if that helps - I really do need to debug my extension :
> ( Not sure if this will help as it all worked on Friday!!! I am
> suspicious that the M$ Debug run-time libraries are not being
> found....
>
>
> kind regards
> Julian

You can try dependency walker, to see if your system finds all the 
required DLLs (i.e. the debug ones of Visual Studio).

George

On Jun 7, 5:41=C2=A0pm, Georgios Petasis <peta...@iit.demokritos.gr> wrote:
> =CF=83=CF=84=CE=B9=CF=82 7/6/2010 19:27, O/H JHJL =CE=AD=CE=B3=CF=81=CE=
=B1=CF=88=CE=B5:
>
>
>
>
>
> > Hi folks
>
> > Last week I was happily debugging my C DLL tcl extension using Visual
> > Studio. Today tclsh85 refuses to load the extension generating an
> > alert dialog quoting an R6034 run-time error. If I recompile the
> > extension as a Release rather than Debug I can load and use the DLL as
> > normal. I'm mystified.
>
> > Has anyone else encountered this (it seems to do with M$ manifest
> > files) and can suggest a way forward? Tomorrow, I plan to rebuild Tcl/
> > Tk etc from source with Debug on (I am currently using ActiveTcl
> > 8.5.8) and see if that helps - I really do need to debug my extension :
> > ( Not sure if this will help as it all worked on Friday!!! I am
> > suspicious that the M$ Debug run-time libraries are not being
> > found....
>
> > kind regards
> > Julian
>
> You can try dependency walker, to see if your system finds all the
> required DLLs (i.e. the debug ones of Visual Studio).
>
> George- Hide quoted text -
>
> - Show quoted text -

Thanks Georgios

A combination of your dependency walker suggestion and the advice in
http://www.insidercoding.com/post/2008/07/21/Debugging-issues-with-MSVCR90D=
LL.aspx
(found via the wonderful http://stackoverflow.com/) led me to discover
that MSVCR90.dll and MSVCR90D.dll were being linked. I told VS2008 to
ignore the former and all is now working.

Still mystified why this happened in the first place but happy now
that I can get on debugging

kind regards
Julian