Version: KSVG test: 0.1 (using KDE KDE 3.2.3) Installed from: Debian testing/unstable Packages Please reassign this to the ksvg product; I couldn't do so when filing this. From Debian Sarge as of 2004-8-2. I know (now) that you're not supposed to feed html to svgdisplay, but thought I'd report the crash anyway. Thank you for an excellent suite of products. Krishna Sethuraman % svgdisplay http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-animate-elem-13-t.html [program starts up and crashes] % svgdisplay --version Qt: 3.2.3 KDE: 3.2.3 KSVG test: 0.1
Cannot reproduce, KSVG 3_4_BRANCH
Blah, I should have read report better: Program received signal SIGSEGV, Segmentation fault. DOM::Node::handle (this=0x0) at ../../khtml/dom/dom_node.h:863 863 NodeImpl *handle() const { return impl; } (gdb) bt full #0 DOM::Node::handle (this=0x0) at ../../khtml/dom/dom_node.h:863 this = (Node *) 0x0 #1 0x281c3cbe in KSVG::SVGElement::SVGElement (this=0xbfbfe3c0, other=0x0) at SVGElement.cc:57 this = (SVGElement *) 0xbfbfe3c0 #2 0x281c234c in KSVG::SVGSVGElement::SVGSVGElement (this=0xbfbfe3c0, other=0x0) at SVGSVGElement.cc:72 this = (SVGSVGElement *) 0xbfbfe3c0 #3 0x281b97b3 in KSVG::SVGDocument::rootElement (this=0x811a960) at SVGDocument.cc:106 this = (SVGDocument *) 0x811a960 #4 0x8053bd9 in SVGTestWidget::slotRenderingFinished (this=0x80d4c00) at SVGTestWidget.cc:52 this = (SVGTestWidget *) 0x80d4c00 rect = {x1 = 0, y1 = 0, x2 = 449, y2 = 449} test = {<Element> = {<Node> = {impl = 0x28071000, _vptr$ = 0x408}, <No data fields>}, impl = 0x80d4c00} #5 0x8053711 in SVGTestWidget::qt_invoke (this=0x80d4c00, _id=45, _o=0xbfbfe544) at SVGTestWidget.moc:82 this = (SVGTestWidget *) 0x80d4c00 #6 0x297b4f01 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3 No symbol table info available. #7 0x282276c2 in KSVG::SVGDocumentImpl::finishedParsing (this=0x80d4d00, t0=true, t1=@0x8142130) at SVGDocumentImpl.moc:157
is this bug still valid under kde 4 ?
This component has been replaced with the QtSvg based "svgpart" in KDE 4. If this issue still needs to be addressed, please add a comment.