[apport] akregator crashed with SIGSEGV in QCString::replace()

Bug #96537 reported by dresnu
This bug report is a duplicate of:  Bug #51070: Akregator crashed on fetch/on exit. Edit Remove
2
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kdepim

Akregator crashed while logging out

ProblemType: Crash
Architecture: i386
Date: Mon Mar 26 17:25:51 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/akregator
Package: akregator 4:3.5.6-0ubuntu5
PackageArchitecture: i386
ProcCmdline: akregator -icon akregator -miniicon akregator -caption Akregator
ProcCwd: /home/dresnu
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 QCString::replace () from /usr/lib/libqt-mt.so.3
 KConfigINIBackEnd::parseSingleConfigFile ()
 KConfigINIBackEnd::parseConfigFiles ()
 KConfigBase::parseConfigFiles ()
 KConfig::reparseConfiguration ()
Uname: Linux toshi 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
dresnu (dresnu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:QCString::contains (this=0xbf74ef58, rx=@0xb77e6871) at tools/qcstring.cpp:1855
KConfigINIBackEnd::parseSingleConfigFile (this=0xb3fe748, rFile=@0xbf74f090, pWriteBackMap=0x0, bGlobal=false, bDefault=false)
KConfigINIBackEnd::parseConfigFiles (this=0xb3fe748) at /build/buildd/kdelibs-3.5.6/./kdecore/kconfigbackend.cpp:403
KConfigBase::parseConfigFiles (this=0xbf74f250) at /build/buildd/kdelibs-3.5.6/./kdecore/kconfigbase.cpp:1673
KConfig::reparseConfiguration (this=0xbf74f250) at /build/buildd/kdelibs-3.5.6/./kdecore/kconfig.cpp:174

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.