On 22/10/2010 20:51, Andre Poenitz wrote:
> Hi.
>
> On Fri, Oct 22, 2010 at 05:46:37PM +0200, Abdelrazak Younes wrote:
>
>>> Could you send the debugger log (right pane of Windows->Views->Debugger
>>> Log) ? It would be nice to have this reproducible here...
>>>
>> Well I only have " Windows->Views->Log" here, which opens up two
>> panes.
>>
> That's the one. It went through its yearly renamings recently...
>
>
>> dEnableReverseDebugging: true (default: false) ***
>>
> Here we go. Switch "Reverse Debugging" off, and I am pretty sure the
> problem will be gone.
>
Aha... thanks! Could never figured this by myself... always nice to have
a friend among Qt-creator's developers :-)
>
>> [...]
>> sStep next requested...
>> <27-exec-next
>>
>>> 27^running
>>> *running,thread-id="1"
>>> ~"Process record doesn't support instruction 0xfef at address
>>>
>> 0x7f2224a1ce41.\n"
>>
>>> &"Process record: failed to record execution log.\n"
>>> *stopped,reason="signal-received",signal-name="0",signal-meaning="Signal
>>> 0",frame={addr="0x00007f2224a1ce40",func="??",args=[],from="/lib/libc.so.6"},thread-id="1",stopped-threads="all",core="0"
>>>
> The feature is not really robust in gdb, and if it fails, it produces
> errors that do not match other error conditions. I am trying to make
> Creator recognize those situations one-by-one...
>
I trust you on this.
Cheers,
Abdel.
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator
