Bug 162024 - tla crashes when it makes update tree
tla crashes when it makes update tree
Product: Fedora
Classification: Fedora
Component: tla (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On: 158655
Blocks: FE5Target
  Show dependency treegraph
Reported: 2005-06-29 04:59 EDT by Michael
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version: 1.3.3-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-16 12:40:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
tla crash back trace (3.67 KB, text/plain)
2005-06-29 05:00 EDT, Michael
no flags Details

  None (edit)
Description Michael 2005-06-29 04:59:35 EDT
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):

How reproducible:

Steps to Reproduce:

Additional info:
Comment 1 Michael 2005-06-29 05:00:54 EDT
Created attachment 116113 [details]
tla crash back trace
Comment 2 Shahms E. King 2005-06-29 10:49:18 EDT
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 17:44:09 EST
Does 1.3.3-3 work better for you?
Comment 4 Shahms E. King 2006-02-16 12:11:53 EST
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 12:40:59 EST
Assuming fixed, feel free to reopen if the problem persists.

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