|
Red Hat Bugzilla – Full Text Bug Listing |
| Summary: | [abrt] crash in publican-1.6.2-0.fc12: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Publican | Reporter: | Nathan Thomas <nathan> | ||||||||||||||
| Component: | publican | Assignee: | Jeff Fearn <jfearn> | ||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | low | ||||||||||||||||
| Version: | 1.6 | CC: | jfearn, mmcallis, publican-list, r.landmann | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | abrt_hash:66ff2e665c137f4cad4edfc549e2855d0974d827 | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2010-11-06 08:52:33 EDT | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Nathan Thomas
2010-05-10 10:52:50 EDT
Created attachment 412864 [details]
File: backtrace
Created attachment 412866 [details]
Example script being used to call Publican
Hi Nathan, I've tested this on RHEL and F12 and can't duplicate this crash. Can you attach ca-ES.log from a broken run? Also if you are running publican 1.6.2 you can add '--nocolours' to avoid having ansi colour codes in the log. Created attachment 413239 [details]
Example log file
Hi,
The old log files were overwritten when I ran the script again, here is an example log from a failed build.
Nathan
Hi Nathan, not much help in there either :( Can you try enabling debug mode and manually building a language that fails? Debug mode was already enabled. Upgrading to 1.6.3 still results in crashes, but the files build successfully and produce complete log files (see attached examples). Created attachment 415119 [details]
publican 1.6.3 backtrace
Created attachment 415121 [details]
publican 1.6.3 example log from crashed build
Hi Nathan, the trace is showing a crash in libxslt, I'm not quite sure how it's trying to double free something. Can you paste the output of: $ rpm -q libxslt perl-XML-LibXSLT FWIW I still can't duplicate this crash, nor have I heard of anyone else having it :( Created attachment 418164 [details]
Cleaned up script
Just thought I'd add my take on what the build script should look like.
(In reply to comment #9) > Hi Nathan, the trace is showing a crash in libxslt, I'm not quite sure how it's > trying to double free something. > > Can you paste the output of: > > $ rpm -q libxslt perl-XML-LibXSLT > > FWIW I still can't duplicate this crash, nor have I heard of anyone else having > it :( Hi Jeff, Here's the output: libxslt-1.1.26-1.fc12.x86_64 perl-XML-LibXSLT-1.68-4.fc12.x86_64 I've upgraded to Publican 1.99, but haven't had chance to test it yet (I've packed everything away, moving house in two days!) - I'll let you know when I do, and I'll try your cleaned up script too. Many thanks! Nathan This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Hi, I'm no longer experiencing this problem with Publican 2.x. Cheers Nathan |