[Qt-creator] Qt Creator debugging problems

Andre Poenitz andre.poenitz at nokia.com
Wed Feb 18 10:35:38 CET 2009


On Tue, Feb 17, 2009 at 08:28:40AM +0200, Jaco Naude wrote:
> Hi
>
> I'm still struggling with debugging in Qt Creator. After initially thinking
> that it only happens in 0.92 RC1, I realized that it happened in 0.91 Beta
> as well after testing it. According to some feedback it seems like it is a
> problem with plugins loaded in Qt Creator, especially Webkit. I'm not using
> webkit in my application, and I also don't have Safari installed on my pc.
>
> Any ideas would be greatly appreciated. The debugger stops and goes into a
> loop like the following every time I try to continue or step through the
> code:
> > Running...
> > Stopped.
> > Finished retrieving data
> > Stopped: "signal received"
>
> Below I've added the output of the GDB View panes in Qt Creator. First I've
> pasted the contents of the leftmost pane, followed by the contents of the
> rightmost pane.

Thanks, that does the job ;-)

> gdb.exe -i mi --tty=\\.\pipe\creator-è

This looks strange for starters. Looks someone is confusing numbers
and strings here...  Should do no direct harm in this case, though
(and will be fixed tonight)

> [...]
> 15:24:08.296
> stdout:~"GNU gdb 6.3\n"

This is not the gdb that's distributed with the Windows bundle, is it?
We test only with gdb >= 6.7.50 (the one in the bundle).

Everything else works only out of sheer luck - if at all.

> input:[15:24:08.265] 12-data-list-register-values x
> stdout:12^error,msg="mi_cmd_data_list_register_values: No registers."

[This looks like e.g. register listing seems not to work with 6.3's MI...]

> input:[15:24:08.625] 16-exec-run
> [...]
> stdout:16*stopped,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation
> fault",thread-id="1",frame={addr="0x7c96df51",func="ntdll!RtlpNtMakeTemporaryKey",args=[],from="ntdll.dll"}

Ok, and a crash early in the application startup before the first
"regular" breakpoint was hit. That was not indeed not caught until
very recently. It should be fixed in (very) recent snapshots, though.

Andre'






More information about the Qt-creator-old mailing list