Hi Johnny,
Thanks for your response. Actually Mr. Dougs response to check with ACE
version 5.4.2 worked for me and I am not getting this corruption issues with
this version of ACE. There were few minor compilation issues with this
release of ACE but they were quite easy to resolve.
Regards,
Meenakshi
-----Original Message-----
From: Johnny Willemsen [mailto:jwillemsen@remedy.nl]
Sent: Sunday, November 28, 2004 11:46 PM
To: Meenakshi Vohra; ace-bugs@cs.wustl.edu
Subject: RE: test program failed on running Static library of ACE 5.4 /
5.4.1 / 5.3.1 on AMD 64 Windows platform
Hi,
Thanks for using the PRF form.
Do I understand correctly you are using Windows 64 bit and the 64bit
Microsoft compiler? This is a platform that is not tested yet and it seems
that there are still some problems. Because such a simple program doesn't
work maybe compiler/linker options could be the problem. We have here AMD64
with SuSE 92 Linux without problems, AMD64 with a normal windows xp and the
normale vc71 compiler also doesn't have problems.
Maybe you can investigate this and supply patches, or else look at
http://www.cs.wustl.edu/~schmidt/commercial-support.html for companies that
deliver ACE/TAO support. We as Remedy IT can also solve this for you, see
www.theaceorb.nl for our services.
Regards,
Johnny Willemsen
Remedy IT
Leeghwaterstraat 25
2811 DT Reeuwijk
The Netherlands
www.theaceorb.nl / www.remedy.nl
> ACE VERSION: 5.4 / 5.4.1 / 5.3.1
>
> HOST MACHINE and OPERATING SYSTEM:
> Windows 2003 Server - AMD64 bit platform:
>
> TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
> COMPILER NAME AND VERSION (AND PATCHLEVEL):
> Compiler Version 14.00.40310.23 for AMD64 using Microsoft Platform SDK
> Linker Version 8.00.40310.23 using Microsoft Platform SDK
>
> CONTENTS OF $ACE_ROOT/ace/config.h [if you use a link to a
> platform-
> specific file, simply state which one]:
> config.h
>
> CONTENTS OF
> $ACE_ROOT/include/makeinclude/platform_macros.GNU (unless
> this isn't used in this case, e.g., with Microsoft Visual C++):
>
> CONTENTS OF
> $ACE_ROOT/bin/MakeProjectCreator/config/default.features
> (used by MPC when you generate your own makefiles):
> Makefile (ace_lib64.mak modified to include compiler flag
> /GS- and linker flag /machine:AMD64
>
> AREA/CLASS/EXAMPLE AFFECTED:
> [What example failed? What module failed to compile?] The following
> test program on same AMD 64 bit Windows machine.
>
> #include <stdlib.h>
>
> #include <stdio.h>
>
> #include <wchar.h>
>
> #include <ace/INET_Addr.h>
>
> int main(int argc, char **argv) {
>
> ACE_INET_Addr addr;
>
> addr.set(2821, "meenakshi.yahoo.com");
>
> // addr.set("meenakshi.yahoo.com:2821");
>
> printf("port=%d host=%s\n", addr.get_port_number(),
> addr.get_host_name());
>
> return 0;
>
> }
>
>
>
> DOES THE PROBLEM AFFECT:
> COMPILATION? No
> LINKING? No
> On Unix systems, did you run make realclean first?
> EXECUTION?
> OTHER (please specify)?
> [Please indicate whether ACE, your application, or both are affected.]
> the test application
> SYNOPSIS:
> A simple test program as mentioned above failed on running Static
> library (aces.lib) of ACE 5.4 / 5.4.1 on AMD 64 Windows platform
>
> DESCRIPTION:
>
>
> I tried building ACE 5.3.1 and on suggestions 5.4, and 5.4.1 on an
> AMD 64 bit Windows platform. After that I tried to run the above
> mentioned test program with static ace release library (aces.lib).
>
> The output was always some junk or crash and debugging gave me a hint
> that as soon as ::set fn. is called the parameter values become,
> invalid looks like a stack corruption.
>
> I verfied that all library versions did get built successfully on
> AMD64 platform by doing needed build changes.
>
>
> REPEAT BY:
>
> just rebuild ACE with above mentioned couple of changes in the
> ace_lib64.mak file and try running this test program.
>
>
> SAMPLE FIX/WORKAROUND:
> not known
>
>
> Regards,
> Meenakshi
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
> Please suggest,
>
> Thanks,
>
> Meenakshi
>
>
>
>