From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: Attached test case using signals crashes when run in compatibility mode under EM64T. Same application in native mode runs fine. Version-Release number of selected component (if applicable): kernel-2.4.21-20.EL How reproducible: Always Steps to Reproduce: 1. compile the program sig32_test.c using -m32 flag 2. Run the program 3. Actual Results: Either the testcase crashes with SIGSEGV or it just hangs. Expected Results: Same test case when compiled with "-m64" passes fine. Additional info:
Created attachment 103709 [details] Failing test case # gcc -m32 sig32_test.c # ./a.out Segmentation fault # gcc sig32_test.c # ./a.out #
Created attachment 103710 [details] Failing test case # gcc -m32 sig32_test.c # ./a.out Segmentation fault # gcc sig32_test.c # ./a.out #
Created attachment 103711 [details] Patch fixing the issue
Our partners product a Java Virtual Machine, does not run on RH EL 3 (64-bit) on the EM64T platform. This is important for us to have a 32- bit JVM run on the 64-bit OS on our EM64T enabled platforms. It runs without changes on the RHEL 4 (beta) on EM64T. Sample testcase was representative of what the virtual machine uses.
Geoff Gustafson posted the patch in comment #3 on 11/10 for consideration in U5.
A fix for this problem has just been committed to the RHEL3 U5 patch pool this evening (in kernel version 2.4.21-27.7.EL).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-294.html