I have a C++ shared object library that I am calling from an OpenEdge (Progress) application. The program makes library calls to a C++ function that uses the "stringstream" data type. Even if I just DECLARE a stringstream data type, the Progress application core dumps with a Memory violation. I don't even need to USE the variable, just making the declaration causes the problem.
What makes it even more disturbing, is that at one point, it worked fine. I have no idea what I have changed between now and the time it was working. I do have a previously compiled version of the library that works which uses the stringstream datatypes.
The problem was related to conflicting included libraries. I had copied some libraries into a directory that caused some confusion with the compiler. Fortunatly, all the libraries I copied were owned by a different user. I was able to delete all those libraries and the program began working again.