debugger/profiler lotus dll crashes server - how to tackle this as a non expert

[Olaf Kittelmann]

Hi,
I have little experience in c++ coding that goes back to the
university days, - not so far back for me.

our company developed a couple of notes applications including c++ dll
components.
The author of these dlls (and with him the entire c++ kno-how) has
left long before I came aboard, which makes me the c++ "expert" now.

One of our notes applications causes our customers domino server to
crash after operating times between 4 hours and 5 days. the customer
suspects memory leak problems caused by the dll - I myself have not
seen any logs or msgs yet.

The server runs in windows environment and I use win 2000

I am aware this info is very vague, but it is all I got.

I am wondering which strategy to apply to solve this.
-I do not expect to find the fault by looking at the source.
-I reckon I need to reproduce the fault conditions and then use a
debugger
and a profiler to understand what is going on.
- are there any platform/ compiler issues (like which compiler was
used...- don't know, I code java)?

regards

Olaf Kittelmann

 

[Phlip]

our company developed a couple of notes applications including c++ dll
components.
The author of these dlls (and with him the entire c++ kno-how) has
left long before I came aboard, which makes me the c++ "expert" now.

Your best option will be the newsgroup that covers your compiler. The
effects of bugs are platform-specific, and

One of our notes applications causes our customers domino server to
crash after operating times between 4 hours and 5 days. the customer
suspects memory leak problems caused by the dll - I myself have not
seen any logs or msgs yet.

Run your Win32 "Performance Monitor", and for the Notes app see if memory
goes up. But this won't tell you the variable that's doing it.

Look at the string handling code (attending to functions like strdup()).

Then, look up a non-Standard function called _heapwalk, and use it in
various places in the code to look for situations where new blocks arrive on
the heap.

- are there any platform/ compiler issues (like which compiler was
used...- don't know, I code java)?

Well, now you see the error of your ways.