> "Useless" is a bit strong as far as I can tell. I am not aware of any > open show-stoppers in JIRA right now, and in the admittedly rare > cases where I use it it appears to work. But functionality-wise it's > certainly not on par with GDB-on-something-like-Fedora. >
Yes, useless. If I create an executable, linked to static library (all within a SUBDIR in Creator) and attempt to trace into call into a function defined within the static library, GDB will fail 95% of the time. And by fail I mean, I mean any of these cases: 1) I'll get no symbols in the expression panel at all. 2) I'll get the symbols but no values (Creator will claim that they are optimised out, which is untrue). 3) Creator will hang while break-points flicker on an off widely. 4) GDB will hang and it, Creator and the app under test must be force-quit using Activity Monitor. This is true with both C and C++ code and is a daily occurrence for me. The pretty-printers are similarly unreliable: I'm lucky if I can see the contents of a QString. STL types never work. If I clean out the debugging helpers, and rebuild them, they MAY work for one or two sessions, before going bonkers again. This stuff used to work better back when Creator was first released. My understanding is that something was changed in the debugger integration in v2 (something to do with python pretty-printers)? Ever since then it's been a crapshoot on Mac. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
