gdb backtrace burpage ...

[Michael Meeks]

Hi Tom,

	Thanks for jumping in :-)

On Wed, 2012-06-13 at 11:57 -0600, Tom Tromey wrote:
> Michael> But is there any way of suppressing that warning thrash 
> Michael> for the case where it is not enabled ?
> 
> There's no way to disable it.
> File a feature request in gdb bugzilla if you want that.

	I did that:

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

> I looked into this a little.  The warning here is peculiar.
> Despite what it says, gdb is not actually looking for an RTTI symbol.
> Instead it is just looking for the debug info for the indicated type.

	Interesting.

> I don't know a simple way to reproduce this problem, or I would dig
> into it a bit more.  My guess is that it can only be reproduced in
> relatively odd situations, like where you have some subset of the
> debuginfo, but not quite all of it.

	I linked the python pretty-printers we use into the bug; I think if you
just delete the debuginfo for libfwklo.so (actually - safer to delete
all-but-vcl perhaps :-) and put a breakpoint in the 'Window::Show'
method, a simple run of almost any version of LibreOffice should show
the issue.

	Thanks !

		Michael.

-- 
michael.meeks at suse.com  <><, Pseudo Engineer, itinerant idiot