On Mon 17 Sep 2012 23:45:26 Nick Boyce escribió:
[snip]
> Thanks for the explanation - I think I'm beginning to get the hang of it
> now, though would very much like to understand how some function names can
> remain unresolvable while others in the same package (libglib in this
> instance) are not
Am Dienstag, 18. September 2012 schrieb Nick Boyce:
> > Similar it goes for others like:
> >
> >
> > #19 0x7f801b4d96f2 in g_main_context_dispatch () from
> > /lib/libglib-2.0.so.0 #20 0x7f801b4dd568 in ?? () from
> > /lib/libglib-2.0.so.0
> > #21 0x7f801b4dd71c in g_main_context_itera
On Wednesday 12 Sep 2012 13:32:48 Martin Steigerwald wrote:
> > Actually (answering my own question), looking at just the first 4 stack
> > frames ... I could use my superpowers to deduce perhaps the missing
> > debug symbols are the ones for D-Bus :-)
> >
> > Would I be right ?
>
> Yes. You use
Hi Nick,
Am Mittwoch, 12. September 2012 schrieb Nick Boyce:
> On Tuesday 11 Sep 2012 21:13:15 Nick Boyce wrote:
> > Can anyone help me figure out how to proceed in order to get useful
> > crash dumps from Dolphin ?
>
> It's been suggested to me off-list that if I posted the entire
> backtrace it
On Tuesday 11 Sep 2012 21:13:15 Nick Boyce wrote:
> Can anyone help me figure out how to proceed in order to get useful crash
> dumps from Dolphin ?
It's been suggested to me off-list that if I posted the entire backtrace it
might help someone see which debug symbols I need, so I've attached it
I had a Dolphin crash the other day, but the crash handler was unable to
obtain a useful stack trace - see screenshot here :
http://www.glimmer.adsl24.co.uk/images/Dolphin-20120910.png
At first I assumed that - in the usual way - I needed to install Dolphin debug
symbols to get a useful stack tr
6 matches
Mail list logo
