kile crashed with SIGSEGV in QBasicAtomicInt::ref()

Bug #405187 reported by Luis Silva
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kile (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kile

Happens when running pdflatex.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Jul 27 10:04:56 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kile
Package: kile 1:2.1.0~svn981319beta1-1ubuntu1 [modified: usr/bin/kile]
ProcCmdline: /usr/bin/kile /home/username/Doutoramento/tex/These/tese_de_doutoramento.kilepr
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
SegvAnalysis:
 Segfault happened at: 0x8bc0a62 <_ZN7QStringaSERKS_+34>: lock incl (%eax)
 PC (0x08bc0a62) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kile
StacktraceTop:
 QBasicAtomicInt::ref (this=0x946574c, other=...)
 QString::operator= (this=0x946574c, other=...) at tools/qstring.cpp:1131
 _start ()
Title: kile crashed with SIGSEGV in QBasicAtomicInt::ref()
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Luis Silva (lacsilva) wrote :
Revision history for this message
Luis Silva (lacsilva) wrote :

Some more info.
Running the sequence:
>pdflatex
>bibtex
>pdflatex
>pdflatex
works smoothly outside kile.
After doing this, compiling from within kile desn't make it crash anymore.
Removing all the output files and trying to compile from within kile makes it crash again.

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QString::operator= (this=0x946574c, other=@0xa1f5e30)
LatexOutputFilter::flushCurrentItem (this=0x9465720)
LatexOutputFilter::detectWarning (this=0x9465720,
LatexOutputFilter::parseLine (this=0x9465720,
OutputFilter::Run (this=0x9465720, logfile=@0xbfef2578)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kile (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

Does this still happen when using kile beta2 in final karmic?

Changed in kile (Ubuntu):
assignee: nobody → Andreas Wenning (andreas-wenning)
status: New → Incomplete
Revision history for this message
Luis Silva (lacsilva) wrote :

Just tried it and yes, it still happens with kile beta2 in final karmic.

Changed in kile (Ubuntu):
assignee: Andreas Wenning (andreas-wenning) → nobody
status: Incomplete → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in kile (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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