Bug 101318 - Quanta crashes when VPL or VPL and Source Editor are chosen
Summary: Quanta crashes when VPL or VPL and Source Editor are chosen
Status: RESOLVED DUPLICATE of bug 99826
Alias: None
Product: quanta
Classification: Unmaintained
Component: VPL (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Paulo Moura Guedes
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-11 20:07 UTC by Steve Taylor
Modified: 2005-07-18 20:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Taylor 2005-03-11 20:07:14 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Mandrake RPMs
OS:                Linux

How to Reproduce: Select "VPL" or "VPL and Source Editor" from menu or toolbar.
SIGABRT (SIGNAL 6) is result.

Quanta Plus 3.3 running with KDE 3.3.2 on Mandrake Linux 10.2 beta 3

Backtrace report from KDE Crash Handler follows:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1238227264 (LWP 9945)]
[KCrash handler]
#7  0xffffe410 in ?? ()
#8  0xbfffe17c in ?? ()
#9  0x00000006 in ?? ()
#10 0x000026d9 in ?? ()
#11 0xb634d705 in raise () from /lib/tls/libc.so.6
#12 0xb634f099 in abort () from /lib/tls/libc.so.6
#13 0xb6522d67 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#14 0xb65208f5 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#15 0xb6520932 in std::terminate () from /usr/lib/libstdc++.so.6
#16 0xb6520ab2 in __cxa_throw () from /usr/lib/libstdc++.so.6
#17 0xb7bd5583 in DOM::Node::insertBefore (this=0x0, newChild=@0x0, 
    refChild=@0x0) at dom_node.cpp:264
#18 0x08258998 in QExtFileInfo::staticMetaObject ()
#19 0x08282c69 in htmlDocumentPropertiesui::staticMetaObject ()
#20 0x0827ee0f in htmlDocumentPropertiesui::staticMetaObject ()
#21 0x08280712 in htmlDocumentPropertiesui::staticMetaObject ()
#22 0x080bae18 in ?? ()
#23 0x084aca68 in ?? ()
#24 0x0929fa20 in ?? ()
#25 0x00000000 in ?? ()
#26 0x082915f0 in typeinfo name for QGList ()
#27 0x0929ad00 in ?? ()
#28 0x082dbba8 in typeinfo for KTextEditor::MarkInterfaceExtension ()
#29 0x0929ad00 in ?? ()
#30 0xbfffe950 in ?? ()
#31 0x0929ad00 in ?? ()
#32 0x00000006 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000006 in ?? ()
#35 0x00000010 in ?? ()
#36 0x085ed208 in ?? ()
#37 0xb6ea5c52 in typeinfo name for QPtrList<QToolBar> ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0xb6f5c574 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0x083a1c90 in ?? ()
#40 0x083be920 in ?? ()
#41 0xbfffea70 in ?? ()
#42 0x08086bc6 in ?? ()
#43 0x0929ad00 in ?? ()
#44 0x082dbba8 in typeinfo for KTextEditor::MarkInterfaceExtension ()
#45 0x082915f0 in typeinfo name for QGList ()
#46 0x00000000 in ?? ()
#47 0x017a3070 in ?? ()
#48 0x085ed29c in ?? ()
#49 0x00000128 in ?? ()
#50 0x00000128 in ?? ()
#51 0x083a1c90 in ?? ()
#52 0x083be920 in ?? ()
#53 0xbfffea70 in ?? ()
#54 0x080d0bb2 in ?? ()
#55 0x0929ad00 in ?? ()
#56 0x00000001 in ?? ()
#57 0xb62e19d0 in _XInitIM ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
Comment 1 Philippe Rigault 2005-03-12 03:16:04 UTC
Cannot reproduce on 3.3.2 compiled from sources, Fedora Core 3.
A Mandrake problem maybe ?
Comment 2 Steve Taylor 2005-03-12 04:37:59 UTC
On Friday March 11, 2005 18:16, Philippe Rigault wrote:
[bugs.kde.org quoted mail]

Philippe,

It might be. I reported it because I could crash Quanta *every* time doing 
this.

Would reporting it here be enough for the Mandrake team to see it, or should I 
talk to them directly?
Comment 3 Philippe Rigault 2005-03-12 05:18:38 UTC
> Would reporting it here be enough for the Mandrake team to see it, or should
> I talk to them directly?
In general, when using a package from your distro (as opposed to building from sources), it is a good idea to report bugs to your distro first:
 - if the bug is specific to your distro, it avoids clogging KDE with bugs that are not their problem. Many crash bugs can be distro-specific, given the dependencies on glibc/gcc/kernel and so on.
  - if the but is really from KDE, then your distro maintainer will file a bug in KDE (or tell you to do so yourself), so it eventually gets to the right place (here).

In this case, now that you suspect a distro-specific behaviour, you should absolutely file a bug in your distro.
Remember, a bug not filed does not exist, so don't count on Mandrake eyes to magically see it and act on it. Report the bug, then it exists.

Cheers.
Comment 4 Paulo Moura Guedes 2005-07-18 20:21:29 UTC

*** This bug has been marked as a duplicate of 99826 ***