security_cookie unresolved symbol

[Rick Jones]

I'm using Visual C++ .NET (V7) along with the beta version of the SDK so I
can use x64 (AMD64) compiler. I launch a Win Svr 2003 x64 Build Env (Retail,
PreRelease) window then issue a devenv/useenv at the command prompt to start
the .NET IDE. I also modifed the project so it places the target files in
their approprate target folder. The problem is when I build my project I get
a link error of undefined symbol for security_cookie. If I build the same
project using the x86 environments all is fine.

What library is security_cookie in or how do I fix this unresolved external
symbo errorl?

Thanks,

Rick

[Gary Chang[MSFT]]

Hi Rick,

I'm using Visual C++ .NET (V7) along with the beta version of the SDK so I
can use x64 (AMD64) compiler. I launch a Win Svr 2003 x64 Build Env (Retail,PreRelease) window then issue a devenv/useenv at the command prompt to
the .NET IDE. I also modifed the project so it places the target files in
start their approprate target folder.

AFAIK, the Windows Server 2003 64-Bit Build Environment is used to set the
build environment for the command-line building in its opening console
window, but not for the VS.NET IDE. It will not configure the VS.NET IDE's
setting for building 64-bit application automatically, and I am not
entirely clear about what's the appropriate target folder you modified?

And besides, the Visual C++ 2003's compiler is not fully support compiling
the application targeting AMD64 processor; the Visual C++ 2005 ("Whidbey")
will include fully supported compilers for targeting both AMD64 and
Itanium. So I suggest you build your 64-Bit application in the command-line
and then it will use the corresponding compiler and libraries from your
64-Bit SDK package.

By the way, the "security_cookie" is defined in the VC run-time library,
such as MSVCRTD.LIB and MSVCRT.LIB.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

[Rick Jones]

Gary,

I followed the article posted at
http://www.devx.com/amd/Article/21313/2046 to set up VS to allow building an
x64 app within the IDE. What I mean by modifying the target folder is that I
defined my own build configuration for the AMD64 build and set the target so
I would not get any x86 overlap in the target folder. As part of the AMD64
configuration I set the linker to /machine:amd64. It uses the amd64 compiler
and linker so that seems to work except for the unresolved symbol. When I
add MSVCRTD.LIB or MSVCRT.LIB it does not help I still get the error.

I assume I have to create a make file to do what you suggest (build on
the command line), but unfortunately .NET 2003 no longer exports make files.

"Gary Chang[MSFT]" <v-******@online.microsoft.com> wrote in message
news:jd**************@TK2MSFTNGXA01.phx.gbl...

Hi Rick,

I'm using Visual C++ .NET (V7) along with the beta version of the SDK so I
can use x64 (AMD64) compiler. I launch a Win Svr 2003 x64 Build Env

(Retail,

PreRelease) window then issue a devenv/useenv at the command prompt to
the .NET IDE. I also modifed the project so it places the target files in
start their approprate target folder.

AFAIK, the Windows Server 2003 64-Bit Build Environment is used to set the
build environment for the command-line building in its opening console
window, but not for the VS.NET IDE. It will not configure the VS.NET IDE's
setting for building 64-bit application automatically, and I am not
entirely clear about what's the appropriate target folder you modified?

And besides, the Visual C++ 2003's compiler is not fully support compiling
the application targeting AMD64 processor; the Visual C++ 2005 ("Whidbey")
will include fully supported compilers for targeting both AMD64 and
Itanium. So I suggest you build your 64-Bit application in the
command-line
and then it will use the corresponding compiler and libraries from your
64-Bit SDK package.

By the way, the "security_cookie" is defined in the VC run-time library,
such as MSVCRTD.LIB and MSVCRT.LIB.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Gary Chang[MSFT]]

Hi Rick

I followed the article posted at
http://www.devx.com/amd/Article/21313/2046 to set up
VS to allow building an x64 app within the IDE.
...

In this scenario, I suggest you can add the following lib to your program's
link, to see does it work for you?

%MsSDK%\Lib\AMD64\bufferoverfl-owu.lib

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

[Rick Jones]

Thanks that worked, but now I get unresolved link errors during the debug
build. The following are not found:

RTC_InitBase
RTC_Shutdown
RTC_CheckStackVars

I removed the Basic RTC setting in the compiler setup (C/C++ Code
Gerneration setup), but I still get the errors.

Thanks,
Rick

"Gary Chang[MSFT]" <v-******@online.microsoft.com> wrote in message
news:1N**************@TK2MSFTNGXA01.phx.gbl...

Hi Rick

I followed the article posted at
http://www.devx.com/amd/Article/21313/2046 to set up
VS to allow building an x64 app within the IDE.
...

In this scenario, I suggest you can add the following lib to your
program's
link, to see does it work for you?

%MsSDK%\Lib\AMD64\bufferoverfl-owu.lib

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Gary Chang[MSFT]]

Hi Rick,

Thanks that worked, but now I get unresolved link errors during the debug
build. The following are not found:

RTC_InitBase
RTC_Shutdown
RTC_CheckStackVars

I removed the Basic RTC setting in the compiler setup (C/C++ Code
Gerneration setup), but I still get the errors.

The runtime checks /RTC are not supported in Platform SDK. Even compiler
that comes with PSDK considers this as a valid switch. However the PSDK
comes with version of CRT that is currently used in Win2k3 SP1. It is based
on VC6 CRT and was modified by the Windows team. This version of CRT does
not contain code required for /RTC to work.

So I think you need to remove the /GS compiler switch in the debug build
configuration of your 64bit application as well.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

[Rick Jones]

When I get the unresolves, the /GS and /RTC switchs are not set. I do have
two project one works the other does not. The difference is that the one
that works uses /MTd switch the one that doesn't work uses /MDd switch.
AlsoI just upgraded to the released version of the PSDK.

Rick
"Gary Chang[MSFT]" <v-******@online.microsoft.com> wrote in message
news:PD*************@TK2MSFTNGXA01.phx.gbl...

Hi Rick,

Thanks that worked, but now I get unresolved link errors during the debug
build. The following are not found:

RTC_InitBase
RTC_Shutdown
RTC_CheckStackVars

I removed the Basic RTC setting in the compiler setup (C/C++ Code
Gerneration setup), but I still get the errors.

The runtime checks /RTC are not supported in Platform SDK. Even compiler
that comes with PSDK considers this as a valid switch. However the PSDK
comes with version of CRT that is currently used in Win2k3 SP1. It is
based
on VC6 CRT and was modified by the Windows team. This version of CRT does
not contain code required for /RTC to work.

So I think you need to remove the /GS compiler switch in the debug build
configuration of your 64bit application as well.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Gary Chang[MSFT]]

Hi Rick,

When I get the unresolves, the /GS and /RTC switchs are not set. I do have
two project one works the other does not. The difference is that the one
that works uses /MTd switch the one that doesn't work uses /MDd switch.
AlsoI just upgraded to the released version of the PSDK.

When using the /MDd switch, the compiler will place the library MSVCRTD.LIB
into the target .obj file instead of the LIBCMTD.LIB(in case of usng the
/MTd).

Basicly, those unresolved symbol errors will occur when you debug the 64
bit code with /GS swithch, since you have already removed it from your
project, the problem may be in the MSVCRTD.LIB of the new PSDK, but we
haven't repro it now.

Do you have compared the compile command line of those 2 projects, is there
any other difference except the MTd/MDd switch?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

[Rick Jones]

The following (which is the one that does not work) are the differences
between the two projects:

/D "_USRDLL" /D "_WINDLL" /D "_AFXDLL" /D "_MBCS" /MDd /W4 /TP

Rick

"Gary Chang[MSFT]" <v-******@online.microsoft.com> wrote in message
news:J1**************@TK2MSFTNGXA01.phx.gbl...

Hi Rick,

When I get the unresolves, the /GS and /RTC switchs are not set. I do have
two project one works the other does not. The difference is that the one
that works uses /MTd switch the one that doesn't work uses /MDd switch.
AlsoI just upgraded to the released version of the PSDK.

When using the /MDd switch, the compiler will place the library
MSVCRTD.LIB
into the target .obj file instead of the LIBCMTD.LIB(in case of usng the
/MTd).

Basicly, those unresolved symbol errors will occur when you debug the 64
bit code with /GS swithch, since you have already removed it from your
project, the problem may be in the MSVCRTD.LIB of the new PSDK, but we
haven't repro it now.

Do you have compared the compile command line of those 2 projects, is
there
any other difference except the MTd/MDd switch?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Gary Chang[MSFT]]

Hi Rick,

The following (which is the one that does not work) are the differences
between the two projects:

/D "_USRDLL" /D "_WINDLL" /D "_AFXDLL" /D "_MBCS" /MDd /W4 /TP

Thanks for the information, but I could't repro the problem on my side,
meanwhile I have also searched our internal database for your problem, but
did not find any similar case like yours.

So in the current scenario, I think the most efficient way for you to
resolve this issue is to contact one of our PSS support engineers to work
with you. This may need you submit a support incident in Microsoft PSS
(Product Support Service). As a MSDN subscriber, you have two free support
incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.

For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-[phone] or by
choosing one of the options listed at
http://support.microsoft.com/d-efaul...Offe-rProPhone
If there is anything unclear, please feel free to post here. We are glad to
be of assistance.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.