I recently started using static libs with Qt Creator and found a bug that means if you build a project that depends on a lib (and the lib has changed but the project using it hasn't, it will compile the lib but it *won't* re-link it. This caused me some debugging grief very similar to what you have described. I thought I was going nuts at the time.
I reported this earlier this week and am hoping it will be fixed soon. 2009/7/17 KC Jones <[email protected]>: > This is a first time post, so sorry if I'm missing something obvious. > > I've been debugging my QT4.5 app in Creator v1.1 and 1.2 on OS X 10.5.7, and > I've been having intermittent, but frequent, problems debugging. What I > *think* I'm observing is that breakpoints are honored and work OK the first > time, but when I do an incremental build, they do not work reliably. The > debugger breaks at a wrong location or does not break at all. When I > perform a full rebuild of my project, breakpoints seems to work OK. > > This is different from the debug helper issues that I see in the list > archives. > > It is very similar to the "Breakpoints not working" issue I see here: > http://lists.trolltech.com/pipermail/qt-creator/2009-May/002865.html and, > like that user, I also migrated my .pro file from an older project that was > originally created in VS on Windows. But, unlike this case, my .pro file > does not include the 'CONFIG += release' issue. I've also verified that my > compile steps include the '-g' option. > > My project consists of three sub projects, the main Qt application plus two > static library projects. Not sure if that is potentially relevant or not. > > Any suggestions on how to solve this, or at least isolate the problem > better? > > KC > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-creator > > _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
