Bug 162024

Summary: tla crashes when it makes update tree
Product: [Fedora] Fedora Reporter: Michael <misha>
Component: tlaAssignee: Ville Skyttä <scop>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: scop, shahms
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: 1.3.3-3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-16 17:40:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 158655    
Bug Blocks: 162161    
Attachments:
Description Flags
tla crash back trace none

Description Michael 2005-06-29 08:59:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686; en) Opera 8.0

Description of problem:
When I ty to update existing project tree tla crashes with error:
*** glibc detected *** tla: double free or corruption (!prev): 0x0a690cc0 ***


Version-Release number of selected component (if applicable):
tla-1.3.1-4.fix.1

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  

Additional info:

Comment 1 Michael 2005-06-29 09:00:54 UTC
Created attachment 116113 [details]
tla crash back trace

Comment 2 Shahms E. King 2005-06-29 14:49:18 UTC
Thanks for the bug report, although that traceback isn't terribly useful as it's
lacking any symbol information...

I have RPMS for the most recent version of tla that fixes this problem, but they
have some issues on PPC and the build system won't push them until they build
successfully on all support platforms.

I recommend using bazaar until the PPC issues are resolved (well, I recommend
using bazaar in general, but I digress).

Comment 3 Ville Skyttä 2006-02-01 22:44:09 UTC
Does 1.3.3-3 work better for you?

Comment 4 Shahms E. King 2006-02-16 17:11:53 UTC
Ville, I'm going to assign this bug to you.  I suspect it is fixed in 1.3.3-3,
but since the reporter hasn't said anything for ~6 months we'll never know. 
Feel free to close it if you think it's appropriate.

Comment 5 Ville Skyttä 2006-02-16 17:40:59 UTC
Assuming fixed, feel free to reopen if the problem persists.