public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "michael.meeks at suse dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14235] New: verbose RTTI message polluting traces
Date: Thu, 14 Jun 2012 11:05:00 -0000	[thread overview]
Message-ID: <bug-14235-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14235

             Bug #: 14235
           Summary: verbose RTTI message polluting traces
           Product: gdb
           Version: 7.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: michael.meeks@suse.com
    Classification: Unclassified


We have number of python pretty-printers for LibreOffice to make our component
system much more usable and helpful in gdb. Unfortunately this doesn't handle
the case where we don't compile the whole project with debugging symbols.

We don't compile the whole project like that due to the time it takes, and the
huge size of the result (making the development interation slower) not least
with ld / gdb :-)

Anyhow - with partial symbols eg. symbols missing for the libfwklo.so when
generating a backtrace from a breakpoint in vcl's

void Window::Show( sal_Bool bVisible, sal_uInt16 nFlags )

method (going through framework at some stage) - I get:

(gdb) bt
#0  Window::Show (this=0x8a7cf28, bVisible=1 '\001', nFlags=0)
at /data/opt/libreoffice/master/vcl/source/window/window.cxx:6180
#1  0xb784d187 in SfxFrame::SfxFrame (this=0x8a7cde0,
i_rContainerWindow=..., i_bHidden=false)
    at /data/opt/libreoffice/master/sfx2/source/view/frame2.cxx:338
#2  0xb784d6f1 in SfxFrame::Create (i_rFrame=warning: RTTI symbol not
found for class 'framework::Frame'
warning: RTTI symbol not found for class 'framework::Frame'
warning: RTTI symbol not found for class 'framework::Frame'
warning: RTTI symbol not found for class 'framework::Frame'

    uno::Reference to {<com::sun::star::lang::XComponent> =
{<com::sun::star::uno::XInterface> = {_vptr.XInterface = 0xb163c4f0},
<No data fields>}, <No data fields>})
at /data/opt/libreoffice/master/sfx2/source/view/frame2.cxx:315

where the:

warning: RTTI symbol not found for class 'framework::Frame'

is quite annoying :-)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-06-14 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 11:05 michael.meeks at suse dot com [this message]
2012-06-14 11:08 ` [Bug python/14235] " michael.meeks at suse dot com
2012-06-14 11:10 ` michael.meeks at suse dot com
2013-01-30  9:28 ` jan.kratochvil at redhat dot com
2013-01-30  9:47 ` jan.kratochvil at redhat dot com
2013-02-12 17:10 ` andre.poenitz at digia dot com
2013-02-13 10:11 ` michael.meeks at suse dot com
2013-02-13 21:02 ` tromey at redhat dot com
2013-02-15 19:19 ` tromey at redhat dot com
2013-02-15 21:26 ` tromey at redhat dot com
2013-02-16  2:29 ` tromey at redhat dot com
2013-02-25 15:36 ` muhammad_bilal at codesourcery dot com
2013-02-25 15:54 ` muhammad_bilal at codesourcery dot com
2013-02-25 16:18 ` jan.kratochvil at redhat dot com
2014-02-16 19:20 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14235-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).