Debugging helpers vanish when QFileDialog is instantiated

Brief description: Gdb loses contact with debugging helpers on the moment when running inferior instantiates QFileDialog

Elaborate Description: I have debugging helpers running correctly, done full rebuild (removed the provided qtc-debugging-helper folder etc.). I use them smoothly until a QFileDialog is instantiated. NOT displayed yet, exec() not called, just instantiated. Just before instantiation, "Recheck debugging availability" shows still correct "Dumper version 1.35, 55 custom dumpers found" On step over the instantiation (dialog still not displayed), debugged values which require helpers vanish from "Locals and Watchers" and debugger status changes permanently to "Debugging helpers not found". Gdb continues to work normally, breaking and displaying observed values, but only the basic types.

I have also a parallel Qt Creator 1.3.0 installation on a Linux Ubuntu 8.04 in a VirtualBox 1.6.4. Behavior there is correct all the time.

I suspect the warning "while parsing target library list: not well-formed (invalid token)" (this doesn't show up on Linux) but i have no idea where it originates (gdb?) and why. It also shows paralelly in the "Application output" pane. Google on exact match returns 4 (total of four) hits, where only one vaguely related to Qt is in russian and gives no solution.

Attached is a package containing

• total minimal example project. The debug-helper dependent value being observed is QString testStr.
• screenshot displaying breakpoint locations
• set of gdb log files. Right/left is a gdb log panel location. "Pre" means up to the point of QFileDialog instantiation (first breakpoint). "Post" is on the step over instantiation and further.

I may also suspect some relation to a win32 shell extensions which i use (so called Tortoise[SVN|CVS|HG]) because on QFileDialog execution (that is, exec() call), the Application output was full of related debug messages. But i have uninstalled them all as part of the issue isolation. Now there are no shell related messages, but the described gdb malfunction persists.