When I add my library to the workspace with Add Dynamic Module and run with RootCause, my application never starts. Whats wrong and how can I fix it?
Add Dynamic Module causes a library to be “preloaded” (using the aprobe -dll option) because it’s only on program startup that automatic trace configuration can be done. However, some user libraries cannot be preloaded because they rely on some global state being defined which isn’t done until the program starts running. On Unix platforms, this (currently) means you can’t trace or do anything else on this module. You’re beat unless you can change the library to allow it to be pre-loaded. However, on Windows there is partial support for probing modules that are loaded after program startup. In particular, you can use custom probes, but you can’t use the predefined probes which use the “probe all” feature. We wrote a subset of the trace probe for a customer to use on his dynamically loaded Windows library: dyntrace.apc. Give it a try and/or contact us for help.
