Bug 118671
Summary: | Error parsing at spec file on ia64 with IBM 1.3.1 JVM | ||
---|---|---|---|
Product: | [Retired] Red Hat Developer Suite | Reporter: | Jeremy Handcock <handcock> |
Component: | RPM Plug-in | Assignee: | Matt Newsome <mnewsome> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0 | CC: | aaron, patrickm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-05-05 07:58:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeremy Handcock
2004-03-18 19:41:04 UTC
I had the same problem when exporting the pump RPM/SRPM in the test plan, but only on the IBM JVM. Works fine on JRockit. I also got the IBM JVM to dump core once when exporting the pump RPM. This JVM is looking worse and worse. Happens on x86 with IBM JVM, only got it with the "at" rpm the others look fine. Seems pretty likely it's a jvm issue. Got it again exporting PUMP, hadn't made any changes to the spec file. Forgot to throw in these that showed up on the console when doing the export on pump, these didn't show up with the import on at though Unhandled event loop exception Reason: java.lang.NullPointerException Unhandled event loop exception Reason: java.lang.NullPointerException Unhandled event loop exception Reason: java.lang.NullPointerException Forgot to mention, the jvm I was using was jre-1.4.2-ibm This happens with IBM's 1.4.2 on ia64 now as well (but not BEA's). I have the same problem about parsing the specfile on the IBM 1.4.2 JVM on RHEL3, but only with the pump source RPM. I get double characters when I enter data into the patch tag name. This problem does not occur with the BEA JVM or the Sun JVM. Closing this bug out due to its age and the assigned product. |