Bug 63777 - kompare back trace when selecting
Summary: kompare back trace when selecting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdesdk
Version: 7.3
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-18 18:05 UTC by Ben Levenson
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-21 16:44:08 UTC
Embargoed:


Attachments (Terms of Use)
kompare-backtrace (3.42 KB, text/plain)
2002-04-18 18:06 UTC, Ben Levenson
no flags Details

Description Ben Levenson 2002-04-18 18:05:35 UTC
Description of Problem: 
Kompare occassionally backtraces while trying to jump to a specific 
'Difference' via the drop down menu. 
      
Version-Release number of selected component (if applicable):      
  kdesdk-kompare-3.0.0-5  
  tree: Valhalla-re0417.1 
 
How Reproducible:      
90% -- you might have to jump to several diff points before the app crashes. 
 
Steps to Reproduce:      
1. kompare two text files 
2. Use the 'Difference' drop down menu to jump to a specific diff. 
3. repeat until crash -- typically, 5 or less jumps will result in crash 
 
Actual Results: 
  [root@test121 root]# kompare 
  QObject::connect: No such signal KompareModelList::status(enum  
Kompare::Status) 
  QObject::connect:  (sender name:   'unnamed') 
  QObject::connect:  (receiver name: 'kompare_part') 
  QGList::locate: Index -8 out of range 
  KCrash: crashing.... crashRecursionCounter = 2 
  KCrash: Application Name = kompare path = <unknown> pid = 18087 
 
backtrace attachment to follow.

Comment 1 Ben Levenson 2002-04-18 18:06:10 UTC
Created attachment 54404 [details]
kompare-backtrace

Comment 2 Ben Levenson 2004-06-21 16:44:08 UTC
Seems to be working in RHEL3 (kdesdk-3.1.3-1.1) 


Note You need to log in before you can comment on or make changes to this bug.