static and dynamic C runtime libraries?

[John S Dalzell]

Hi,

I have a C++ app which needs to work with a server on a remote machine. The
manufacturer has given us a set of DLL's which provide API calls to send
requests to the server and receive an information feed from it. My app is
compiled under Micro$oft VS.NET 2003 with option /MT to statically link in
the C runtime libraries msvcrt.lib etc. My app has to store information from
the server and answer requests from many remote clients. These requests are
made via an RPC connection.

It works like a charm on the test machine which is a replica of the
production machine. Both are dual processors and all the relevant DLL
versions are the same. I've checked them one by one.
Yet it falls over like a drunken sailor in production with a "Buffer
overrun" exception. I'm thinking that a mismatch between the static and
dynamic libraries might cause this, but why does it work perfectly in test
and not at all in production? There is a production feed from the server to
the test machine and it gets a similar stream of client requests generated
by another program which is running on several machines. The stress on the
test machine is the same, if not more than the production machine.

Free disk space on the prod machine is 1.5GB. There is 27GB free on the test
machine (!), Every time the info feed from the server indicates that
something significant has changed, it must be written to disk.

I realise that this is not much to work with, but does anyone have any ideas
as to why this app would run nicely in test and not in prod when the
environments and transaction volumes are virtually identical?

Regards, JohnD.

[Jack Klein]

On Sat, 18 Jun 2005 15:13:48 GMT, "John S Dalzell"
<jo*********@bigpond.com> wrote in comp.lang.c++:

Hi,

I have a C++ app which needs to work with a server on a remote machine. The
manufacturer has given us a set of DLL's which provide API calls to send
requests to the server and receive an information feed from it. My app is
compiled under Micro$oft VS.NET 2003 with option /MT to statically link in
the C runtime libraries msvcrt.lib etc. My app has to store information from
the server and answer requests from many remote clients. These requests are
made via an RPC connection.

It works like a charm on the test machine which is a replica of the
production machine. Both are dual processors and all the relevant DLL
versions are the same. I've checked them one by one.
Yet it falls over like a drunken sailor in production with a "Buffer
overrun" exception. I'm thinking that a mismatch between the static and
dynamic libraries might cause this, but why does it work perfectly in test
and not at all in production? There is a production feed from the server to
the test machine and it gets a similar stream of client requests generated
by another program which is running on several machines. The stress on the
test machine is the same, if not more than the production machine.

Free disk space on the prod machine is 1.5GB. There is 27GB free on the test
machine (!), Every time the info feed from the server indicates that
something significant has changed, it must be written to disk.

I realise that this is not much to work with, but does anyone have any ideas
as to why this app would run nicely in test and not in prod when the
environments and transaction volumes are virtually identical?

Regards, JohnD.

You need to take this question to a Windows programming group, like
news:comp.os.ms-windows.programmer.win32 or one of Microsoft's support
groups in the news:microsoft.public.* family. The C++ language does
not define or support DLLs, static libraries, or remote calls across a
network, making it off-topic here. Your issue is all about Windows
specific mechanisms, not about the C++ language.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html