Bug 113751 - labplot segfaults
Summary: labplot segfaults
Status: RESOLVED FIXED
: 116135 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Beta 3
Hardware: x86-64 All
: P5 - None : Major
Target Milestone: ---
Assignee: Dirk Mueller
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-29 07:37 UTC by Andreas Vetter
Modified: 2005-10-06 17:05 UTC (History)
3 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Vetter 2005-08-29 07:37:58 UTC 
start labplot from command line:
vetter@wpyc022:~> labplot
Segmentation fault
Comment 1 Dirk Mueller 2005-09-07 09:16:07 UTC 
==3272== Invalid read of size 4 
==3272==    at 0x1C26EAD2: QString::operator=(QString const&) (qshared.h:49) 
==3272==    by 0x1C248753: QDir::QDir(QString const&, QString const&, int, 
int) (qdir.cpp:220) 
==3272==    by 0x1C254512: QGPluginManager::addLibraryPath(QString const&) 
(qgpluginmanager.cpp:314) 
==3272==    by 0x1C256397: QGPluginManager::QGPluginManager(QUuid const&, 
QStringList const&, QString const&, bool) (qgpluginmanager.cpp:296) 
==3272==    by 0x1BF684DF: qt_init_image_plugins() (qpluginmanager_p.h:64) 
==3272==    by 0x1BF68B2B: QImageIO::outputFormats() (qimage.cpp:4369) 
==3272==    by 0x1BF68C17: QImage::outputFormatList() (qimage.cpp:3440) 
==3272==    by 0x1C9F8297: Qwt3D::IO::setupHandler() (qwt3d_io.cpp:159) 
==3272==    by 0x1C9F8694: ??? (qwt3d_io.h:53) 
==3272==    by 0x1CA12345: (within /opt/kde3/lib/libLabPlotqwtplot3d.so.0.2.4) 
==3272==    by 0x1C9DFA34: (within /opt/kde3/lib/libLabPlotqwtplot3d.so.0.2.4) 
==3272==    by 0x1B8EF9A3: call_init (in /lib/ld-2.3.5.so) 
==3272==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
Comment 2 Dirk Mueller 2005-09-07 09:17:07 UTC 
so a QString& is 0...  not sure how that can happen :/
Comment 5 Dirk Mueller 2005-09-07 17:10:26 UTC 
fix submitted
Comment 6 Dirk Mueller 2005-09-09 14:16:09 UTC 
*** Bug 116135 has been marked as a duplicate of this bug. ***