On Saturday, July 10, 2010, Ruben Van Boxem <vanboxem.ruben@...> wrote:
> I have always had trouble with gdb and QtCreator using mingw-w64. Don't know if it's a QtCreator issue or just something on my system, but I'd like of someone else confirmed this for me. Every time I click "debug application (lower left corner), a cmd window pops up, and nothing happens.
> You can use the QtCreator package from "External binary packages". It is x64, so you'll need x64 Windows to test.
> Problem is, you either need to import a CMake project or create a new qmake project :s, which means building Qt. I'd opt for the first, as it saves (a lot) of time. If you have 32-bit Qt and 32-bit mingw-w64, please try as well
> Thanks! Please don't feel obligated, I'm just trying to get some confirmation here :)
> PS: if it's a QtCreator problem, I'll be reporting it as a bug.
note. This is a WAG because I don't have experience with qtcreator but
*everything* that is desired to be debugged must be the same
architecture. The app, gdb (so it can attach) and most likely
my guess is that qtcreator injects a debugbreakprocess into the
running process which means that it needs to be the same arch. You
can't debugbreakprocess a 32 bit app from 64bit and vice versa. You
could be seeing a side effect of this failing.
(one more thing...if this is already the case that everything is the
same we have an issue in 64 bit gcc compiled apps with respect to
setting up the stack unwind info that is also used during debugging
(mingw 64 doesn't yet do this). This causes a debugbreakprocess et
al to not work unless the debugger is already attached to the process.
Hope this helps a bit in your hunt