Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionChristopher Graves
2018-11-08 23:50:48 UTC
Created attachment 1503533[details]
.out file from segmentation fault
Description of problem:
I am compiling the library PALISADE by NJIT. https://git.njit.edu/groups/palisade
I get a segmentation fault during compilation and was told to make a bug report by the system.
Version-Release number of selected component (if applicable):
g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
How reproducible:
Easy to reproduce
Steps to Reproduce:
1. Install lzip via yum 'yum install lzip'
2. Download source code from PALISADE gitlab website https://git.njit.edu/groups/palisade
3. Go into directory and run ./configure.sh
4. Run make
Actual results:
make gmp_all
make[1]: Entering directory `/home/nacs-scan/FHE/PALISADE-master'
make[1]: Nothing to be done for `gmp_all'.
make[1]: Leaving directory `/home/nacs-scan/FHE/PALISADE-master'
make ntl_all
make[1]: Entering directory `/home/nacs-scan/FHE/PALISADE-master'
make[1]: Leaving directory `/home/nacs-scan/FHE/PALISADE-master'
make allcore allpke utall
make[1]: Entering directory `/home/nacs-scan/FHE/PALISADE-master'
g++ -std=gnu++11 -fPIC -g -Wall -Werror -O3 -fopenmp -pthread -I src -Isrc/core/lib -Isrc/pke/lib -I test -I third-party/include -I third-party/include/rapidjson -c -o bin/build/pke/lib/bfv-dcrtpoly-impl.o src/pke/lib/bfv-dcrtpoly-impl.cpp
In file included from src/pke/lib/palisade.h:73:0,
from src/pke/lib/cryptocontext.h:31,
from src/pke/lib/bfv-dcrtpoly-impl.cpp:27:
src/pke/lib/pubkeylp.h:1036:28: internal compiler error: Segmentation fault
ConstCiphertext<Element> ciphertext,
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/ccqsCcdx.out file, please attach this to your bugreport.
make[1]: *** [bin/build/pke/lib/bfv-dcrtpoly-impl.o] Error 1
make[1]: Leaving directory `/home/nacs-scan/FHE/PALISADE-master'
make: *** [all] Error 2
Expected results:
Compile without errors.
Additional info:
I will be reaching out to the PALISADE team also.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2167