| Summary: | subversion emerge with sun-jdk-1.4.2.04 as system vm fails | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Josh Scheid <joshuascheid> |
| Component: | New packages | Assignee: | Paul de Vrieze (RETIRED) <pauldv> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Full log of failed emerge | ||
|
Description
Josh Scheid
2004-08-04 02:50:52 UTC
Created attachment 36738 [details]
Full log of failed emerge
Does this still happen with the 05 revision of the sun jdk? If so, you might want to report it at sun, as it seems like something in the java virtual machine went wrong. OK. I'll take that route. This doesn't block me, since I switched to build with blackdown successfully. Feel free to resolve. The VM dump mentions "An error report file has been saved as hs_err_pid15740.log" That's what Sun will want. Normally, I would expect such a file to be in PWD. It was not. If the build fails, should such files still be laying around in /var/tmp/portage/subversion-1.0.6? I will recreate and look. Stale bug, please reopen if this still happens with current stable subversion/java versions. |