RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1297828 - dvipdf segmentation fault on ppc64le
Summary: dvipdf segmentation fault on ppc64le
Keywords:
Status: CLOSED DUPLICATE of bug 1243784
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ghostscript
Version: 7.2
Hardware: ppc64le
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Kaspar // Dee'Kej
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On: 1250914
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-12 14:50 UTC by Denis Fateyev
Modified: 2016-01-12 17:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-12 17:59:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Denis Fateyev 2016-01-12 14:50:59 UTC
Description of problem:
-----------------------
With my `libtommath` package test build, `dvipdf` fails on rhel7 ppc64le arch:

...
dvipdf tommath
/usr/bin/dvipdf: line 46:  2731 Broken pipe             exec dvips -R -Ppdf $DVIPSOPTIONS -q -f "$infile"
      2732 Segmentation fault      (core dumped) | $GS_EXECUTABLE $OPTIONS -q -P- -dSAFER -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sstdout=%stderr -sOutputFile="$outfile" $OPTIONS -c .setpdfwrite -
...

https://kojipkgs.fedoraproject.org//work/tasks/5945/12515945/build.log

All other archs on the same distribution don't cause any problems:
https://koji.fedoraproject.org/koji/taskinfo?taskID=12515942


Version-Release number of selected component:
-----------------------
ghostscript.ppc64le 0:9.07-18.el7
According to https://kojipkgs.fedoraproject.org//work/tasks/5945/12515945/root.log


How reproducible:
-----------------------
Always, during package build


Steps to Reproduce:
-----------------------
1. Get package to be built (e.g., from a Koji successful build):
https://koji.fedoraproject.org/koji/taskinfo?taskID=12515943
https://kojipkgs.fedoraproject.org//work/tasks/5943/12515943/libtommath-0.43.0-2.el7.src.rpm
2. Run Koji scratch build against this SRPM package


Additional info:
-----------------------
Package build fails on ppc64le in rhel7.
Although it builds fine on ppc64le in f22, f23: http://ppc.koji.fedoraproject.org/koji/tasks?owner=dfateyev&state=all

Comment 2 Denis Fateyev 2016-01-12 16:14:34 UTC
As it turns out, the same problem seen also in current `libtommath` version. There is some workaround not to use `dvipdf` at all:
http://pkgs.fedoraproject.org/cgit/rpms/libtommath.git/commit/?h=epel7&id=7c9593329f1f5e341513a9c58653347471d5c803
But I believe that's no sane tendency.

Comment 3 David Kaspar // Dee'Kej 2016-01-12 17:59:52 UTC
Hello Denis!

Thank you for you bug report. We are already aware of this issue. I'm closing this bug as a duplicate - please refer for the initial bug for more information.

*** This bug has been marked as a duplicate of bug 1243784 ***


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