Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-08 Thread André Pönitz 
On Monday 08 March 2010 11:10:02 ext Guillaume Ménant wrote:
> I have built gdb 7.0.1 and now it finds every librairies but 
> debugging helper is still not found by gdb. Debugging helper
> has to be created by Qt Creator, no ?

Yes, it's created from within the Qt Version selection dialog.

When using gdb 7.0.1 the library itself will not be used, but it
still has to be present in the file system, otherwise Creator 
will nag about it.

This was fixed recently, so with current builds the library will
not be needed at all when using gdb 7.0.1 (and later).

Andre'

___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-08 Thread Guillaume Ménant 




 wrote:

  On Friday 05 March 2010 16:44:44 ext gmenant@orange-ftgroup.com wrote:
  
  
I'm using gdb 6.8, Qt Creator 1.3.1 and Qt 4.5.0 (cross-compiled for ARM)

  
  
The easiest solution would probably to upgrade to a python enabled gdb,
such as the 7.0.1 release. This would magically circumvent all problems
related to the building and deployment of the debugging helper library.

Building gdb from source is pretty straightforward.

Andre'
  

I have built gdb 7.0.1 and now it finds every librairies but debugging
helper is still not found by gdb. Debugging helper has to be created by
Qt Creator, no ?

Thanks for your help,


___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread André Pönitz 
On Friday 05 March 2010 16:44:44 ext gmenant@orange-ftgroup.com wrote:
> I'm using gdb 6.8, Qt Creator 1.3.1 and Qt 4.5.0 (cross-compiled for ARM)

The easiest solution would probably to upgrade to a python enabled gdb,
such as the 7.0.1 release. This would magically circumvent all problems
related to the building and deployment of the debugging helper library.

Building gdb from source is pretty straightforward.

Andre'
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread gmenant.ext 




I'm using gdb 6.8, Qt Creator 1.3.1 and Qt 4.5.0 (cross-compiled for
ARM)

 wrote:

  On Friday 05 March 2010 16:06:07 ext gmenant@orange-ftgroup.com wrote:
  
  
Again, this should be "arm". The value comes from the initial dialog. You can
edit the combo box values to suit your needs.

  
  
What version of Creator is that?

The architecture combobox is editable nowadays.

Andre'

  

*
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.



___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread André Pönitz 
On Friday 05 March 2010 16:06:07 ext gmenant@orange-ftgroup.com wrote:
> Again, this should be "arm". The value comes from the initial dialog. You can
> edit the combo box values to suit your needs.

What version of Creator is that?

The architecture combobox is editable nowadays.

Andre'
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread gmenant.ext 




Christian Kandeler wrote:

  On Friday 05 March 2010 11:00:28 ext gmenant@orange-ftgroup.com wrote:

  
  
I've set the GDB sysroot and debug is now working but there is an issue
 evaluating Qt objects. For example I don't see QString values in the debug
 window.

  
  
This indicates a problem with the Qt debugging helpers.
  

Yes, I think it's my current problem but I don't know yet how to build
"debugging helper". I tryed to go in "Option>Qt" but the "rebuild"
button of my cross-compiled Qt is greyed telling me this directory is
not a valid Qt installation. This cross-compiled version has been
delivered to me by a sub-contrator. Can we create this "debugging
helper" manually ?

  
  
You can see below the interesting parts of my GDB debug log (commented) .
 The sysroot is set to /home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/

{...}



  &"source /home/gdrz9888/dev/gdbstartupfile\n"
  

  
  
I assume this is your server start script?
  

It's my gdb start script (not gdbserver).

  
  
  

  &"set environment LD_PRELOAD
/home/gdrz9888/qtsdk-2010.01/qt/qtc-debugging-helper/libgdbmacros.so\n"
  

  
  
Is this the correct object, i.e. the one for the target (arm) platform? Are 
you deploying it to the target platform?
  

No It's not the correct one but I've not "libgdbmacros.so" file for my
plateform yet and I don't know how to build it.

  
  
  

  &"set architecture i386\n"
  

  
  
Again, this should be "arm". The value comes from the initial dialog. You can 
edit the combo box values to suit your needs.
  

Ok, it should be Arm but I don't find how to customize it. The combobox
is not editable and I didn't found it in the options.

  

Christian

  

Thanks,

Guillaume.
*
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.



___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread André Pönitz 
On Friday 05 March 2010 11:00:28 ext gmenant@orange-ftgroup.com wrote:
> Hello,
> 
> It's me again with my Qt Creator/GDB issues...
> 
> I've set the GDB sysroot and debug is now working but there is an issue 
> evaluating Qt objects. For example I don't see QString values in the debug 
> window.
> 
> You can see below the interesting parts of my GDB debug log (commented) . The 
> sysroot is set to /home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/

Part of the "interesting part" of the log would have been the version of the 
gdb you are using,

> >> It seems Qt is looking for "Debug assistance" (I don't know if 
> >> it's the right name in english) but he's not finding it. What is 
> >> it's purpose ?

To show QStrings and such.

Nowadays with a gdb version capable of using python it should not be needed 
anymore.

Andre'
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread Christian Kandeler 
On Friday 05 March 2010 11:00:28 ext gmenant@orange-ftgroup.com wrote:

> I've set the GDB sysroot and debug is now working but there is an issue
>  evaluating Qt objects. For example I don't see QString values in the debug
>  window.

This indicates a problem with the Qt debugging helpers.

> You can see below the interesting parts of my GDB debug log (commented) .
>  The sysroot is set to /home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/
> 
> {...}
> 
> >&"source /home/gdrz9888/dev/gdbstartupfile\n"

I assume this is your server start script?

> >&"set environment LD_PRELOAD
> > /home/gdrz9888/qtsdk-2010.01/qt/qtc-debugging-helper/libgdbmacros.so\n"

Is this the correct object, i.e. the one for the target (arm) platform? Are 
you deploying it to the target platform?

> >&"set architecture i386\n"

Again, this should be "arm". The value comes from the initial dialog. You can 
edit the combo box values to suit your needs.


Christian
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-03-05 Thread gmenant.ext 




Hello,

It's me again with my Qt Creator/GDB issues...

I've set the GDB sysroot and debug is now working but there is an issue
evaluating Qt objects. For example I don't see QString values in the
debug window. 

You can see below the interesting parts of my GDB debug log (commented)
. The sysroot is set to /home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/

{...}

>&"source /home/gdrz9888/dev/gdbstartupfile\n"
t10:40:25.461
>212^done
tResponse time: source /home/gdrz9888/dev/gdbstartupfile: 0.302 s
t10:40:25.461
t10:40:25.461
>&"set environment LD_PRELOAD
/home/gdrz9888/qtsdk-2010.01/qt/qtc-debugging-helper/libgdbmacros.so\n"
t10:40:25.461
>213^done
tResponse time: set environment LD_PRELOAD
/home/gdrz9888/qtsdk-2010.01/qt/qtc-debugging-helper/libgdbmacros.so:
0.302 s
t10:40:25.461
t10:40:25.461
>&"set architecture i386\n"
t10:40:25.461
>&"Undefined item: \"i386\".\n"
t10:40:25.461
>214^error,msg="Undefined item: \"i386\"."
tResponse time: set architecture i386: 0.299 s

>> I don't know why this variable
is set to this value. Perhaps according to i386 architecture ?! It's
pointing to my x86 Qt library but I think It must point to my device Qt
library.

{...}

>~"0x4800 in ?? () from
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/ld-linux.so.3\n"
t10:40:25.583
>216^done
tResponse time: target remote 192.168.2.202:2345: 0.122 s
dState changed from InferiorStarting(6) to InferiorStopped(13).
dINFERIOR STARTED
sAttaché au processus inférieur.
<217set substitute-path /var/tmp/qt-x11-src-4.6.1
/home/gdrz9888/qtsdk-2010.01/qt
sDéfinit les points d'arrêts...
<218-break-list
t10:40:25.585
t10:40:25.626
>&"set substitute-path /var/tmp/qt-x11-src-4.6.1
/home/gdrz9888/qtsdk-2010.01/qt\n"
t10:40:25.626
>217^done
tResponse time: set substitute-path /var/tmp/qt-x11-src-4.6.1
/home/gdrz9888/qtsdk-2010.01/qt: 0.041 s
t10:40:25.626
t10:40:25.626

{...}

>220*stopped,reason="breakpoint-hit",bkptno="1",thread-id="1",frame={addr="0xa566",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbea05d14"}],file="main.cpp",fullname="/home/gdrz9888/dev/local/KeycodeTester/main.cpp",line="10"}
dState changed from InferiorRunning(10) to InferiorStopping(11).
dState changed from InferiorStopping(11) to InferiorStopped(13).
<221call (void*)qDumpObjectData440(1,221+1,0,0,0,0,0,0)
<222p (char*)&qDumpOutBuffer
<223p 4
t10:40:27.990
t10:40:28.041
>&"call (void*)qDumpObjectData440(1,221+1,0,0,0,0,0,0)\n"
t10:40:28.041
>&"No symbol \"qDumpObjectData440\" in current context.\n"
t10:40:28.041
>221^error,msg="No symbol \"qDumpObjectData440\" in current context."
tResponse time: call (void*)qDumpObjectData440(1,0.051+1,0,0,0,0,0,0):
%2 s
t10:40:28.041
t10:40:28.041
>&"p (char*)&qDumpOutBuffer\n"
t10:40:28.041
>&"No symbol \"qDumpOutBuffer\" in current context.\n"
t10:40:28.041
>222^error,msg="No symbol \"qDumpOutBuffer\" in current context."
tResponse time: p (char*)&qDumpOutBuffer: 0.051 s
sAssistance au débogage non trouvée.

>> It seems Qt is looking for
"Debug assistance" (I don't know if it's the right name in english) but
he's not finding it. What is it's purpose ?

{...}

>&"info shared\n"
t10:40:28.301
>~"From    To  Syms Read   Shared Object Library\n"
t10:40:28.302
>~"0x4800  0x40017b24  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/ld-linux.so.3\n"
t10:40:28.302
>~"0x401e3454  0x40890b14  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libQtGui.so.4\n"
t10:40:28.302
>~"0x409f091c  0x409f0f20  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libts-1.0.so.0\n"
t10:40:28.302
>~"0x409fd6c8  0x40a10828  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libpng12.so.0\n"
t10:40:28.302
>~"0x40a23570  0x40a5944c  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libfreetype.so.6\n"
t10:40:28.302
>~"0x40ab416c  0x40b73cf4  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libQtNetwork.so.4\n"
t10:40:28.302
>~"0x40c18d80  0x40dafea4  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libQtCore.so.4\n"
t10:40:28.302
>~"0x40e9f6a8  0x40ea6c84  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libz.so.1\n"
t10:40:28.302
>~"0x40eb45a0  0x40eb7c2c  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/librt.so.1\n"
t10:40:28.302
>~"0x40ec28d0  0x40ec365c  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/libdl.so.2\n"
t10:40:28.302
>~"0x40ed0ca0  0x40edd734  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/libpthread.so.0\n"
t10:40:28.302
>~"0x40f2ad50  0x40f82698  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/usr/lib/libstdc++.so.6\n"
t10:40:28.302
>~"0x40fa8190  0x4100bbcc  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/libm.so.6\n"
t10:40:28.302
>~"0x4104d230  0x41053fb8  Yes
/home/gdrz9888/dev/BSP/eeebook_oe/tmp/rootfs/lib/libgcc_s.so.1\n"
t10:40:28.302
>~"0x41071770  0x4114b760  Yes
/home/gdrz9888/dev/BSP/

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-02-25 Thread Christian Kandeler 
On Thursday 25 February 2010 16:01:38 ext gmenant@orange-ftgroup.com 
wrote:

> I'm using Qt Creator 1.3.1.
> About the sysroot, I don't know what I have to put in it (which path). It's
>  probably my main problem though ! GDB is looking for libQtGui.so.4 in
>  /usr/lib and the file is there (see below). I don't understand why he
>  doesn't find it...

Gdb needs to find the libraries from the target device on the host as well, to 
display debug information. I assume the Qt libs it finds in /usr/lib are the 
x86 versions. You have to tell gdb where on your PC to find the set of target 
libraries. The easiest way to do that is to put a copy of the device OS' file 
system tree on the host system (only libraries and perhaps header files are 
needed) and point the sysroot variable to the respective directory.
Example:
- You copy the relevant files from your device to the directory 
/usr/share/cross on your PC, preserving the directory structure.
- Now you have directories such as /usr/share/cross/lib, 
/usr/share/cross/usr/lib, /usr/share/cross/usr/include etc.
- Then you set gdb's sysroot variable to /usr/share/cross
- gdb should now pick up the right libraries

>> Which commands do you send to gdb when manually debugging?> 
> 
> Nothing for now but Qt Creator sends a lot of commands and I don't know why
>  and how to configure them.

Well, it must get the right sysroot from somewhere. Perhaps it has been set up 
with the correct sysroot at configure time? You can check that by starting gdb 
and typing "show sysroot".

>>> 2 - What is the purpose of gdb startup file and gdbserver startup file ?
>>> What is the syntax ?
> 
>> It's an sh script intended for doing preparations on the server side, like
>> copying your program or starting gdbserver. See the email you referenced
>>  above for an example.
> 
> Ok, I will try it when other points will be ok. Even with a embedded linux
>  on my target, I will be able to copy and lanch gdbserver automatically ?

Yes, scp/ssh can do that.


Christian
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-02-25 Thread gmenant . ext 




Thanks for your answer Christian !

Christian Kandeler wrote:

  Hi,

  
  
I'm currently trying to debug remotely an application through gdb using
Qt Creator. Majo had the same issue previously
(http://www.mail-archive.com/qt-creator@trolltech.com/msg02532.html) but
I don't know what was its final results.

--

State of the art :

I've gdbserver on my device and gdb on my host.
Gdb is configured into Qt Creator (Tools>Options>Debug>Gdb) without gdb
startup script.
My application is built using the right compiler (out of Qt Creator)
My application is on the device.

--

Procedure :

I launch my application using gdbserver on the device : gdbserver
host:port ./application
I start debugging using gdb in Qt Creator : Debug>Start Debugging>Start
and attach to remote application (using i386 option)

--

  
  
The architecture should match your target, i.e. arm. (Shouldn't matter though, 
since your cross-debugger doesn't not support i386 anyway.)
Also, have you set the sysroot?
And which version of Creator are you using?

  

I'm using Qt Creator 1.3.1.
About the sysroot, I don't know what I have to put in it (which path).
It's probably my main problem though ! GDB is looking for libQtGui.so.4
in /usr/lib and the file is there (see below). I don't understand why
he doesn't find it...

>&"warning: .dynamic section for \"/usr/lib/libQtGui.so.4\" is
not at the expected address (wrong library or version mismatch?)\n"

  
  
Log on the device console :

  
  
[ ... ]

  
  
 >&"/lib/ld-linux.so.3: No such file or directory.\n"

  
  
This looks to be the main problem. Again: Have you set the correct sysroot?

  
  
Questions :

1 - Gdbserver is logging an error : "gdbserver: error initializing
thread_db library: version mismatch between libthread_db and libpthread"
and I have not this error when I'm debugging remotely without Qt
Creator. I guess it is due to commands sent by Qt creator to gdb. How
can we configure the commands sent by Qt Creator to gdb/gdbserver ?

  
  
Which commands do you send to gdb when manually debugging?
  

Nothing for now but Qt Creator sends a lot of commands and I don't know
why and how to configure them.

  
  
2 - What is the purpose of gdb startup file and gdbserver startup file ?
What is the syntax ?

  
  
It's an sh script intended for doing preparations on the server side, like 
copying your program or starting gdbserver. See the email you referenced above 
for an example.

  

Ok, I will try it when other points will be ok. Even with a embedded
linux on my target, I will be able to copy and lanch gdbserver
automatically ?

  
  
 If you are not the intended addressee of this
 message, please cancel it immediately and inform the sender.

  
  
How do I know if I'm the intended addressee? Anyway, you are hereby informed 
that I received this message.
  

Sorry for this message, it's automatically generated...

  

Christian

  

*
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.



___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Re: [Qt-creator] Remote debugging armv5te using Qt Creator

2010-02-24 Thread Christian Kandeler 
Hi,

> I'm currently trying to debug remotely an application through gdb using
> Qt Creator. Majo had the same issue previously
> (http://www.mail-archive.com/qt-creator@trolltech.com/msg02532.html) but
> I don't know what was its final results.
> 
> --
> 
> State of the art :
> 
> I've gdbserver on my device and gdb on my host.
> Gdb is configured into Qt Creator (Tools>Options>Debug>Gdb) without gdb
> startup script.
> My application is built using the right compiler (out of Qt Creator)
> My application is on the device.
> 
> --
> 
> Procedure :
> 
> I launch my application using gdbserver on the device : gdbserver
> host:port ./application
> I start debugging using gdb in Qt Creator : Debug>Start Debugging>Start
> and attach to remote application (using i386 option)
> 
> --

The architecture should match your target, i.e. arm. (Shouldn't matter though, 
since your cross-debugger doesn't not support i386 anyway.)
Also, have you set the sysroot?
And which version of Creator are you using?

> Log on the device console :

[ ... ]

>  >&"/lib/ld-linux.so.3: No such file or directory.\n"

This looks to be the main problem. Again: Have you set the correct sysroot?

> Questions :
> 
> 1 - Gdbserver is logging an error : "gdbserver: error initializing
> thread_db library: version mismatch between libthread_db and libpthread"
> and I have not this error when I'm debugging remotely without Qt
> Creator. I guess it is due to commands sent by Qt creator to gdb. How
> can we configure the commands sent by Qt Creator to gdb/gdbserver ?

Which commands do you send to gdb when manually debugging?

> 2 - What is the purpose of gdb startup file and gdbserver startup file ?
> What is the syntax ?

It's an sh script intended for doing preparations on the server side, like 
copying your program or starting gdbserver. See the email you referenced above 
for an example.

>  If you are not the intended addressee of this
>  message, please cancel it immediately and inform the sender.

How do I know if I'm the intended addressee? Anyway, you are hereby informed 
that I received this message.


Christian
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

[Qt-creator] Remote debugging armv5te using Qt Creator

2010-02-23 Thread gmenant . ext 
Hello,

I'm currently trying to debug remotely an application through gdb using 
Qt Creator. Majo had the same issue previously 
(http://www.mail-archive.com/qt-creator@trolltech.com/msg02532.html) but 
I don't know what was its final results.

--

State of the art :

I've gdbserver on my device and gdb on my host.
Gdb is configured into Qt Creator (Tools>Options>Debug>Gdb) without gdb 
startup script.
My application is built using the right compiler (out of Qt Creator)
My application is on the device.

--

Procedure :

I launch my application using gdbserver on the device : gdbserver 
host:port ./application
I start debugging using gdb in Qt Creator : Debug>Start Debugging>Start 
and attach to remote application (using i386 option)

--

Log on the device console :

Process KeycodeTester created; pid = 1074
Listening on port 2345
Remote debugging from host 192.168.2.200
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread
gdbserver: error initializing thread_db library: version mismatch 
between libthread_db and libpthread

--

Log on the Qt Creator gdb console :

sLancer le débogueur pour la chaîne d'outils 'GCC'...
dDebugger settings:
dUseAlternatingRowColours: false  (default: false)
dUseMessageBoxForSignals: true  (default: true)
dAutoQuit: false  (default: false)
dLogTimeStamps: true  (default: false)
dUseDebuggingHelper: true  (default: true)
dUseCustomDebuggingHelperLocation: false  (default: false)
dCustomDebuggingHelperLocation:   (default: )
dDebugDebuggingHelpers: false  (default: false)
dUseCodeModel: true  (default: true)
dUseToolTips: false  (default: false)
dUseToolTipsInLocalsView: false  (default: false)
dUseToolTipsInBreakpointsView: false  (default: false)
dUseAddressInBreakpointsView: false  (default: false)
dUseAddressInStackView: false  (default: false)
dLocation: /my_OE/tmp/cross/armv5te/bin/arm-angstrom-linux-gnueabi-gdb  
(default: gdb)
dEnvironment:   (default: )
dScriptFile:   (default: )
dWatchdogTimeout: 20  (default: 20)
dMaximalStackDepth: 20  (default: 20)
dListSourceFiles: false  (default: false)
dSkipKnownFrames: false  (default: false)
dEnableReverseDebugging: false  (default: false)
dAllPluginBreakpoints: true  (default: true)
dSelectedPluginBreakpoints: false  (default: false)
dNoPluginBreakpoints: false  (default: false)
dSelectedPluginBreakpointsPattern: .*  (default: .*)
dUsePreciseBreakpoints: false  (default: true)
d/home/gdrz9888/dev/test/KeycodeTester/KeycodeTester0xa014960
dState changed from DebuggerNotReady(0) to EngineStarting(1).
dState changed from EngineStarting(1) to AdapterStarting(2).
dTRYING TO START ADAPTER
sNo server start script given. Assuming server runs already.
dSTARTING GDB
dGDB STARTED, INITIALIZING IT
<581show version
<582-interpreter-exec console "help bb"
<583set print static-members off
<584set breakpoint pending on
<585set print elements 1
<586set overload-resolution off
<587handle SIGSEGV nopass stop print
<588set unwindonsignal on
<589set width 0
<590set height 0
<591set environment LD_PRELOAD 
/home/gdrz9888/qtsdk-2010.01/qt/qtc-debugging-helper/libgdbmacros.so
dState changed from AdapterStarting(2) to AdapterStarted(3).
dADAPTER SUCCESSFULLY STARTED
sDémarrage de l'inférieur...
dState changed from AdapterStarted(3) to InferiorStarting(6).
<592set architecture i386
<593-file-exec-and-symbols 
"/home/gdrz9888/dev/test/KeycodeTester/KeycodeTester"
t17:10:08.892
 >~"GNU gdb 6.8\n"
t17:10:08.892
 >~"Copyright (C) 2008 Free Software Foundation, Inc.\n"
t17:10:08.893
 >~"License GPLv3+: GNU GPL version 3 or later 
\n"
t17:10:08.893
 >~"This is free software: you are free to change and redistribute it.\n"
t17:10:08.893
 >~"There is NO WARRANTY, to the extent permitted by law.  Type \"show 
copying\"\n"
t17:10:08.893
 >~"and \"show warranty\" for details.\n"
t17:10:08.893
 >~"This GDB was configured as \"--host=x86 
--target=arm-angstrom-linux-gnueabi\".\n"
t17:10:08.893
t17:10:08.981
 >&"show version\n"
t17:10:08.981
 >~"GNU gdb 6.8\n"
t17:10:08.981
 >~"Copyright (C) 2008 Free Software Foundation, Inc.\n"
t17:10:08.981
 >~"License GPLv3+: GNU GPL version 3 or later 
\n"
t17:10:08.981
 >~"This is fr