DevPartner Studio 9.0

I’ve just updated my installation of DevPartner Studio. I mainly use the C++ error detection part of this suite, that’s the bit that used to be called BoundsChecker. Anyway, version 9.0 is the first version to support VS2008 and x64 so I was quite excited to be able to run the tool on my dev box rather than on my old x86 dev box.

Unfortunately my first impressions aren’t good. Here’s some of the output from the build window whilst the build is being built for “Error detection”. Note the garbled output from some of the “Instrumenting” lines… This looks like a classic case of failing to correctly terminate a string, or a case of reading more memory than you’re supposed to read. Either problem is something that the tool itself should be able to spot if it were ever run on its own code…

3>Generating Code...

3>Instrumenting .\CheckRegistry.cpp

3>Instrumenting .\CompareAndLog.cppGetmonths

4>MockTickCount64Provider.cpp

1>TimeChangeNotificationMonitor.cpp

3>Instrumenting .\StackWalker.cpp¦


3>Instrumenting .\TestException.cppö6
L

3>Instrumenting .\TestLog.cpp6

4>MockThreadPoolWorkerThreadFactory.cpp

1>ThreadPoolCollection.cpp

3>Instrumenting .\TestMonitor.cpp

4>MockThreadPoolMonitor.cpp

1>ThreadPool.cpp

3>Instrumenting .\CallStackCreator.cppÇ

4>MockLocalTimeProvider.cpp

1>ThreadLocalStorage.cpp

4>MockJobMonitor.cpp

1>ThreadedCallbackTimerQueue.cpp

4>MockDirectoryChangeMonitorCallback.cpp

1>ThreadAffinity.cpp

4>MockCollectableThreadPool.cpp

1>Thread.cpp

4>Generating Code...

4>Instrumenting .\MockCollectableThreadPool.cpp

1>TempDirectory.cpp

4>Instrumenting .\MockDirectoryChangeMonitorCallback.cpp

4>Instrumenting .\MockJobMonitor.cppÇ■

1>SystemTime.cpp

4>Instrumenting .\MockLocalTimeProvider.cpp£Ã

4>Instrumenting .\MockThreadPoolMonitor.cpp56

1>StringConverter.cpp

4>Instrumenting .\MockThreadPoolWorkerThreadFactory.cppeck_D_110456

1>SmartStartupInfo.cpp

4>Instrumenting .\MockTickCount64Provider.cppTR

4>Instrumenting .\MockTickCountProvider.cpplib