Re: wchar_t as a string parameter
****
Because these are using esp+8 to compute the address, this means your optimizations have
used Frame Pointer Optimization, where no EBP is maintained. This makes your code very
sensitive to misbehavior of esp. You would want to set a breakpoint here and look at the
value in ecx, which should be the same as szRelease as far as what the debugger tells you.
Record the value that is in esp at this point. That is, the point AT the push instruction
(the stack has not yet been pushed)
if( gf1_RetrieveReleaseLevel(szRelease) )
1000730A lea ecx,[esp+8]
1000730E push ecx
****
AT the push instruction:
szReleaseLevel = 0012fe30
ECX = 0012fe34 [issue?!?!]
ESP = 0012fe2c
****
1000730F call gf1_RetrieveReleaseLevel (1000F990h)
10007314 test eax,eax
Set a breakpoint at this instruction. Look at the value of esp. It had better be the
same as the value you recorded above.
****
AT the test instruction:
ESP = 0012fe2c (same as above)
****
Also, show the command line that is used for both the debug and release builds.
****
RELEASE COMPILE:
/Od /Ob1 /I "C:\E812\System\Include" /I "C:\E812\System\IncludeV" /I
"C:\E812\DEMO\Include" /I "S:\Shared\Include" /I "S:\Shared\Source" /D
"WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D "_VC80_UPGRADE=0x0710" /D
"_WINDLL" /D "_AFXDLL" /D "_UNICODE" /D "UNICODE" /GF /FD /EHsc /MD /Zp1 /Gy
/Zc:wchar_t- /Yu"stdafx.h" /Fp".\Release800/gf1UCA.pch" /Fo".\Release800/"
/Fd".\Release800/" /W3 /nologo /c /Zi /Gz /errorReport:prompt
DEBUG COMPILE:
/Od /I "C:\E812\System\Include" /I "C:\E812\System\IncludeV" /I
"C:\E812\DEMO\Include" /I "S:\Shared\Include" /D "WIN32" /D "_DEBUG" /D
"_WINDOWS" /D "_USRDLL" /D "_VC80_UPGRADE=0x0710" /D "_WINDLL" /D "_AFXDLL"
/D "_UNICODE" /D "UNICODE" /FD /EHsc /RTC1 /MDd /Zp1 /Zc:wchar_t-
/Yu"stdafx.h" /Fp"Debug800/gf1UCA.pch" /Fo"Debug800/" /Fd"Debug800/" /W3
/nologo /c /ZI /Gz /errorReport:prompt
RELEASE LINK:
/Od /I "C:\E812\System\Include" /I "C:\E812\System\IncludeV" /I
"C:\E812\DEMO\Include" /I "S:\Shared\Include" /D "WIN32" /D "_DEBUG" /D
"_WINDOWS" /D "_USRDLL" /D "_VC80_UPGRADE=0x0710" /D "_WINDLL" /D "_AFXDLL"
/D "_UNICODE" /D "UNICODE" /FD /EHsc /RTC1 /MDd /Zp1 /Zc:wchar_t-
/Yu"stdafx.h" /Fp"Debug800/gf1UCA.pch" /Fo"Debug800/" /Fd"Debug800/" /W3
/nologo /c /ZI /Gz /errorReport:prompt
DEBUG LINK:
/OUT:"Debug800\gf1UCA_d.dll" /INCREMENTAL /NOLOGO
/LIBPATH:"S:\Shared\lib\debug800" /DLL /MANIFEST
/MANIFESTFILE:"Debug800\gf1UCA_d.dll.intermediate.manifest"
/DEF:".\gf1UCA.def" /DEBUG /PDB:"Debug800/gf1UCA_d.pdb" /SUBSYSTEM:WINDOWS
/IMPLIB:"Debug800/gf1UCA_d.lib" /MACHINE:X86 /ERRORREPORT:PROMPT gf_d.lib
****
You did not show the function prolog and epilog of gf1_RetrieveReleaseLevel, which is
critical to understanding the interactions here.
****
GF1_API BOOL gf1_RetrieveReleaseLevel(LPTSTR szReleaseLevel)
{
1000F990 sub esp,10h
1000F993 push ebx
1000F994 push ebp
1000F995 push esi
1000F996 push edi
return bReturn;
1000FA9E mov eax,esi
1000FAA0 pop esi
1000FAA1 pop ebp
1000FAA2 pop ebx
}
1000FAA3 add esp,10h
1000FAA6 ret 4
****
By the way, it appears that what might be happening is not that the second time you call
the same function in the same place that you have an error, but that when you pass the
string in to two different functions from two different places in the same subroutine, you
see two different addresses, which is not actually what you said initially.
****
The problem happens the very first time this function is called AND each
time thereafter. I did not mean to convey anything otherwise.
****
You have not said what a GF1_API is, so I have no idea if this is a contributor to the
problem or not; note also that if these have inconsistent definitions between Debug and
Release, I need to know that.
****
#define GF1_API extern "C" __declspec(dllexport) [same for both builds]
Again, I appreciate all the time and help you have put into this. I also
appreciate the advice on things I am not doing correctly.
Jeremy