Re: Squeeze Konqueror Crashes - Need Debug Symbols
On Friday 27 Jul 2012 17:46:38 Martin Steigerwald wrote:
> Am Donnerstag, 26. Juli 2012 schrieb Nick Boyce:
[...]
> > So I have a 3-star backtrace now - thanks everyone, and off to
> > bugs.kde.org I go.
>
> Please have a look whether your backtrace is similar to what I reported:
> Bug 303914 - Crashes on accessing certain URLs
> https://bugs.kde.org/show_bug.cgi?id=303914
Hmm ... I don't know enough about analysing these backtraces, but - assuming I
understand how to determine the call stack that lead to the crash (a big area
of doubt [1]) - then no, I don't think we have similar crashes.
The one in your bug report looks like this (just the first 12 entries) :
Thread 1 (Thread 0x7f97bd3d5760 (LWP 8092)):
[KCrash Handler]
#6 hash (key=...) at rendering/RenderTextControl.cpp:663
#7 hash (key=...) at ../JavaScriptCore/wtf/HashTable.h:281
#8 lookup<WTF::AtomicString, WTF::IdentityHashTranslator<WTF::AtomicString,
WTF::AtomicString, WTF::AtomicStringHash> > (key=..., this=<optimized out>) at
../JavaScriptCore/wtf/HashTable.h:486
#9 contains<WTF::AtomicString, WTF::IdentityHashTranslator<WTF::AtomicString,
WTF::AtomicString, WTF::AtomicStringHash> > (key=..., this=<optimized out>) at
../JavaScriptCore/wtf/HashTable.h:806
#10 contains (key=..., this=<optimized out>) at
../JavaScriptCore/wtf/HashTable.h:329
#11 contains (value=..., this=<optimized out>) at
../JavaScriptCore/wtf/HashSet.h:157
#12 WebCore::RenderTextControl::hasValidAvgCharWidth (family=...) at
rendering/RenderTextControl.cpp:536
[snip]
whereas the crash I experienced looks like this :
Thread 1 (Thread 0x7f895214e760 (LWP 2221)):
[KCrash Handler]
#5 DOM::DocumentImpl::paintDevice (value=0x6c67110, style=0x7105f10,
part=0x724b7c0, op=MinPrefix) at ../../khtml/xml/dom_docimpl.h:378
#6 widthMediaFeatureEval (value=0x6c67110, style=0x7105f10, part=0x724b7c0,
op=MinPrefix) at ../../khtml/css/css_mediaquery.cpp:585
#7 0x00007f8942369793 in khtml::MediaQueryEvaluator::eval (this=0x85d24d0,
expr=0xb26e670) at ../../khtml/css/css_mediaquery.cpp:780
#8 0x00007f894236990a in khtml::MediaQueryEvaluator::eval (this=0x85d24d0,
mediaList=0xafbe4f0, styleSelector=0x9baa0a0) at
../../khtml/css/css_mediaquery.cpp:296
#9 0x00007f894234300c in khtml::CSSStyleSelectorList::append (this=0xd354d60,
sheet=0x921b2f0, medium=<value optimized out>, styleSelector=<value optimized
out>)
at ../../khtml/css/cssstyleselector.cpp:2064
#10 0x00007f8942352f21 in CSSStyleSelector (this=0x9baa0a0, doc=0xcf69b80,
userStyleSheet=<value optimized out>, styleSheets=<value optimized out>,
url=<value optimized out>,
_strictParsing=<value optimized out>) at
../../khtml/css/cssstyleselector.cpp:282
#11 0x00007f89422061e7 in DOM::DocumentImpl::rebuildStyleSelector
(this=0xcf69b80) at ../../khtml/xml/dom_docimpl.cpp:2394
#12 0x00007f894220631d in DOM::DocumentImpl::updateStyleSelector
(this=0xcf69b80, shallow=false) at ../../khtml/xml/dom_docimpl.cpp:2213
[snip]
In both cases we're rendering some content (duh), but it looks like yours
involves Javascript while mine involves CSS.
I don't imagine there's much benefit in comparing our crash symptoms anyway,
given you're using Wheezy/4.8.4 and I'm using Squeeze/4.4.5 - unless it
highlighted common code areas, that .. [cough] .. hadn't improved in two years
:)
> I have several URLs where it crashes 100% reproducably. Two of them in
> above bug report. I didn´t note all of them.
I haven't found a URL which causes the crash reproducibly yet ... I always
have several tabs open at the time, and the only pattern I've noticed is that
clicking 'Back' on one of them is very often the last thing I did. Once the
crash happens, it almost always gets stuck in that state - i.e. I can't resume
the session on Konqueror restart cos the crash just keeps repeating - I have
to start a fresh session to continue surfing.
> Whats strange here is that Konqueror reports:
>
> martin@merkaba:~> konqueror --version
> Qt: 4.8.2
> KDE: 4.8.4 (4.8.4)
> Konqueror: 4.8.3 (4.8.3)
>
> while 4.8.4 packages are installed.
That is bizarre, and seems likely a packaging fault.
It's different here of course :
nick@mybox:~$ konqueror --version
Qt: 4.6.3
KDE Development Platform: 4.4.5 (KDE 4.4.5)
Konqueror: 4.4.5 (KDE 4.4.5)
Good luck :)
[1] I assume that when a backtrace begins with the words "Current thread is
1" then that is the thread which *caused* the crash ... and not the thread
which *handled* the crash, or something silly. I've looked at
http://techbase.kde.org/Development/Tutorials but it doesn't help with this.
BTW: I rather like the sound of the Kubuntu utility 'apport-retrace' described
at https://wiki.kubuntu.org/DebuggingProgramCrash (linked from Techbase) :
"it figures out the set of necessary packages and their
accompanying debug symbol packages, so that the
regenerated stack trace will be fully symbolic"
Cheers,
Nick
--
Never FDISK after midnight
Reply to: