We're working on migrating from CE 3.0 to CE 4.2 for a CEPC. The new
platform seems to be running just fine. We're seeing a significant
difference between the way eVC++ 4.0/CE 4.2 and eVC++ 3.0/CE 3.0 de *** s
handle breakpoints in multi-threaded applications. Under eVC++ 3.0 and CE
3.0, if a break point is encountered in one thread in the process, the other
threads continue execution. In eVC++ 4.0 with CE 4.2, if a break point is
encountered in one thread, ALL the other threads in the process stop
executing. If this is "by design", it's a major setback for us. Our
applications involve real-time control of machinery and the ability to step
through one thread while others continue to execute is of critical
importance. This ability was even present in CE 2.11. I'm sure hoping that
this is a matter of something I omitted from the platform or a setting that
needs to be changed!
Any suggestions will be greatly appreciated!