[Development] Source code path in the debug information

Thiago Macieira thiago.macieira at intel.com
Wed May 16 10:17:31 CEST 2012


On quarta-feira, 16 de maio de 2012 02.49.31, song.7.liu at nokia.com wrote:
> I am trying to copy libQtCore.so.5.0.0 to another different folder to debug
> with my application, but find that I can't step into the source code.
> 
> After look into libQtCore, it seems that the path of source code is relative
> instead absolute, for example as bellow:
> 
> ../../include/QtCore/../../src/corelib/tools/qstring.h:
> qstring.h                                    694            0x15013a
> 
> So is there a way to use the absolute path to build out a debug version of
> libQtCore ? Or does anyone have some idea about this issue?

Those paths are not Qt's doing, but they come instead from the compiler. It 
chooses how to save the path on the debug information.

In the case above, the path is an artifact of the #includes that were 
followed.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120516/65a464c2/attachment.sig>


More information about the Development mailing list