Hi,

ok, I'll try to rephrase (and please correct me if I am wrong):

a) You have a third party application which is closed source and you cannot debug it.
b) This application can be extended by software you create yourself
c) You wrote such an extension and this extension behaves weird when using boost::regex
d) Your extension is a DLL and not a stand-alone program

Correct?

If yes, my first guess is:

You are using dynamic linking and the 3rd party software has its own version of boost::regex linked into it. If this version is different to the one you are using at compile time, weird things are to be expected.

Thus, my first suggestion is to use static linking for your plugin.

Regards,
Roland

Hi,

thanks for the hint!

You've got everything right except d) My extension is a *.exe, but it cannot be run indepently.

I'll try static linking, but I guess it will not solve the problem: I'm 100% sure that the main application does not use boost.regex (I've checked with dependancy walker).

I can debug my plugin (as long as it's not calling functions of the main application library), but I need some hints where to look at when boost::regex is involved.

Regards,
Carsten