[Qt-creator] Debugging Helper broken in 1.2?

[Patric]

Maybe it's not the place to ask this, 
but can you tell me what's also reverse debugging option for and skip known frames when stepping. 
I'm sure this will help another people improve their understanding in QT Creator also. :) 

Regards, 
Patric
  ----- Original Message ----- 
  From: Dat Chu 
  To: qt-creator at trolltech.com 
  Sent: Friday, June 26, 2009 1:09 AM
  Subject: Re: [Qt-creator] Debugging Helper broken in 1.2?


  Debugger helper let you see the content of containers (e.g. vectors, ...) and STL classes (e.g. string) nicely. That way you don't see all these information about: allocator, M_data (i.e. the internal of the implementation) but only see the necessary content. In other words, you get something similar to Visual Studio.

  Dat Chu


  On Thu, Jun 25, 2009 at 4:58 PM, Patric <userqt at gmail.com> wrote:

    Sorry for the question, but what is debugger helper ?
    Anyway, I also installed the new version of QT and QT Creator. But the
    debugger
    is simply not working. A set the breakpoint, start the debugger... and
    nothing. I'll go back to 1.1 .

    Windows XP
    QT 4.5.2
    QT Creator 1.2

    Also I have the same problem with this helper.

    Regards,
    Patric



    ----- Original Message -----
    From: "Robert Caldecott" <robert.caldecott at gmail.com>
    To: <qt-creator at trolltech.com>

    Sent: Friday, June 26, 2009 12:37 AM
    Subject: Re: [Qt-creator] Debugging Helper broken in 1.2?


    > No I do not see the 'nice' contents of any Qt types and the 'use
    > debugging helpers' option always turns itself off. Something isn't
    > right as v1.1 works fine.  My sample created a QString, QMap and a
    > QByteArray, none of which display. What else can I try?
    >
    > On 25 Jun 2009, at 21:34, Andre Poenitz
    > <andre.poenitz at mathematik.tu-chemnitz.de
    > > wrote:
    >
    >> On Thu, Jun 25, 2009 at 09:14:07PM +0100, Robert Caldecott wrote:
    >>> Just installed 1.2 on my home laptop and am having exactly the same
    >>> problem.  Rebuilding the debugging helpers made no difference.  Here
    >>> is my Debugger View pane contents after breaking in the constructor
    >>> of
    >>> a simple MainWindow project (warning: it's a lot of info):
    >>>            21:11:21.156
    >> [...]
    >>
    >>> status:48 custom dumpers found.
    >>
    >>             ^^^^^^^^^^^^ !
    >>
    >>> stdout:~"$3 = 0x707aa740
    >>> \"tdumpers=[\\\"QAbstractItem\\\",\\\"QAbstractItemModel\\\",\\
    >>> \"QByteArray\\\",\\\"QDateTime\\\",\\\"QDir\\\",\\\"QFile\\\",\\
    >>> \"QFileInfo\\\",\\\"QHash\\\",\\\"QHashNode\\\",\\\"QImage\\\",\\
    >>> \"QImageData\\\",\\\"QLinkedList\\\",\\\"QList\\\",\\\"QLocale\\\",\
    >>> \\"QMap\\\",\\\"QMapNode\\\",\\\"QModelIndex\\\",\\\"QMultiMap\\\",\
    >>> \\"QObject\\\",\\\"QObjectMethodList\\\",\\\"QObjectPropertyList\\
    >>> \",\\\"QObjectSignal\\\",\\\"QObjectSignalList\\\",\\\"QObjectSlot\\
    >>> \",\\\"QObjectSlotList\\\",\\\"QSet\\\",\\\"QSharedPointer\\\",\\
    >>> \"QString\\\",\\\"QStringList\\\",\\\"QTextCodec\\\",\\\"QVariant\\
    >>> \",\\\"QVector\\\",\\\"QWeakPointer\\\",\\\"QWidget\\\",\\
    >>> \"basic_string\\\",\\\"list\\\",\\\"map\\\",\\\"set\\\",\\\"string\\
    >>> \",\\\"vector\\\",\\\"wstring\\\",\\\"std::basic_string\\\",\\
    >>> \"std::list\\\",\\\"std::map\\\",\\\"std::set\\\",\\\"std::string\\
    >>> \",\\\"std::vector\\\",\\\"std::wstring\\\",],qtversion=[\\\"4\\\",\
    >>> \\"5\\\",\\\"2\\\"],namespace=\\\"\\\",sizes={int=\\\"4\\\",char*=\\
    >>> \"4
    >> \\\",QString=\\\"4\\\",QStringList=\\\"4\\\",QObject=\\\"8\\
    >> \",QWidget=\\\"20\\\",string=\\\"4\\\",wstring=\\\"4\\\",std::string=
    >> \\\"4\\\",std::wstring=\\\"4\\\",std::allocator=\\\"1\\\"}\""
    >>
    >> Your dumpers got loaded.
    >>
    >> [...]
    >>
    >>> stdout:&"call (void*)qDumpObjectData440(2,34+1,&(s),0,0,0,0,0)\n"
    >>>            21:11:21.593
    >>> [...]
    >>> \"tiname=\\\"local.s\\\",addr=\\\"0x0022FD40\\\",value=\\
    >>> \"VABlAHMAdAA=\\\",valueencoded=\\\"2\\\",type=\\\"QString\\
    >>> \",numchild=\\\"0\\\"\""
    >>
    >> And successfuly used.
    >>
    >> So you don't see the a "nice" display for the "QString s" in your
    >> code?
    >>
    >> Andre'
    >>
    >> _______________________________________________
    >> Qt-creator mailing list
    >> Qt-creator at trolltech.com
    >> http://lists.trolltech.com/mailman/listinfo/qt-creator
    > _______________________________________________
    > Qt-creator mailing list
    > Qt-creator at trolltech.com
    > http://lists.trolltech.com/mailman/listinfo/qt-creator
    >
    >

    > __________ Information from ESET NOD32 Antivirus, version of virus
    > signature database 4098 (20090522) __________
    >
    > The message was checked by ESET NOD32 Antivirus.
    >
    > http://www.eset.com
    >
    >
    >


    __________ Information from ESET NOD32 Antivirus, version of virus signature database 4098 (20090522) __________

    The message was checked by ESET NOD32 Antivirus.

    http://www.eset.com




    _______________________________________________
    Qt-creator mailing list
    Qt-creator at trolltech.com
    http://lists.trolltech.com/mailman/listinfo/qt-creator





------------------------------------------------------------------------------


  _______________________________________________
  Qt-creator mailing list
  Qt-creator at trolltech.com
  http://lists.trolltech.com/mailman/listinfo/qt-creator



  __________ Information from ESET NOD32 Antivirus, version of virus signature database 4098 (20090522) __________

  The message was checked by ESET NOD32 Antivirus.

  http://www.eset.com




__________ Information from ESET NOD32 Antivirus, version of virus signature database 4098 (20090522) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090626/baf6a0b4/attachment.html