You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/10/19 14:57:50 UTC
[jira] Created: (HARMONY-4978) [drlvm][build][EUT] Eclipse3.3
crashes on SLES10 x86
[drlvm][build][EUT] Eclipse3.3 crashes on SLES10 x86
----------------------------------------------------
Key: HARMONY-4978
URL: https://issues.apache.org/jira/browse/HARMONY-4978
Project: Harmony
Issue Type: Bug
Components: DRLVM
Environment: Linux (SLES10) x86
Reporter: Vladimir Beliaev
Priority: Blocker
Recent CC-based automated testing shows 4.45% pass rate for EUT3.3 on Linux x86:
http://people.apache.org/~smishura/r585787/Linux_x86/eut33/
This was caused by moving CC from SLES9 to SLES10 and EUT3.3 start crashing on new OS.
I've double checked the crash - it turned out that I can't just start Eclipsse3.3 on SLES10 x86.
To reproduce:
1. download eclipse-SDK-3.3-linux-gtk.tar.gz from http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500
2. unpack it, enter resulted 'eclipse' directory
3. run the command:
time java -showversion -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -data ./workspace
You'll get the stack dump of about 105-109 frames with the top like:
SIGSEGV in VM code.
Stack trace:
0: little2_nameLength (xmltok.c:-1)
1: MOZ_XML_GetBuffer (??:-1)
2: MOZ_XML_GetBuffer (??:-1)
Could someone take a look? Moving to new platform (SLES9->SLES10) causes "regression" since M3 to be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-4978) [drlvm][build][EUT] Eclipse3.3
crashes on SLES10 x86
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-4978.
----------------------------------------
Resolution: Fixed
I implemented version scripts for linking DRLVM libraries at 587472. Eclipse works for me now with mozilla-xulrunner package installed.
> [drlvm][build][EUT] Eclipse3.3 crashes on SLES10 x86
> ----------------------------------------------------
>
> Key: HARMONY-4978
> URL: https://issues.apache.org/jira/browse/HARMONY-4978
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Linux (SLES10) x86
> Reporter: Vladimir Beliaev
> Assignee: Gregory Shimansky
> Priority: Blocker
> Attachments: patch.patch
>
>
> Recent CC-based automated testing shows 4.45% pass rate for EUT3.3 on Linux x86:
> http://people.apache.org/~smishura/r585787/Linux_x86/eut33/
> This was caused by moving CC from SLES9 to SLES10 and EUT3.3 start crashing on new OS.
> I've double checked the crash - it turned out that I can't just start Eclipsse3.3 on SLES10 x86.
> To reproduce:
> 1. download eclipse-SDK-3.3-linux-gtk.tar.gz from http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500
> 2. unpack it, enter resulted 'eclipse' directory
> 3. run the command:
> time java -showversion -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -data ./workspace
> You'll get the stack dump of about 105-109 frames with the top like:
> SIGSEGV in VM code.
> Stack trace:
> 0: little2_nameLength (xmltok.c:-1)
> 1: MOZ_XML_GetBuffer (??:-1)
> 2: MOZ_XML_GetBuffer (??:-1)
> Could someone take a look? Moving to new platform (SLES9->SLES10) causes "regression" since M3 to be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-4978) [drlvm][build][EUT] Eclipse3.3
crashes on SLES10 x86
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky reassigned HARMONY-4978:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm][build][EUT] Eclipse3.3 crashes on SLES10 x86
> ----------------------------------------------------
>
> Key: HARMONY-4978
> URL: https://issues.apache.org/jira/browse/HARMONY-4978
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Linux (SLES10) x86
> Reporter: Vladimir Beliaev
> Assignee: Gregory Shimansky
> Priority: Blocker
>
> Recent CC-based automated testing shows 4.45% pass rate for EUT3.3 on Linux x86:
> http://people.apache.org/~smishura/r585787/Linux_x86/eut33/
> This was caused by moving CC from SLES9 to SLES10 and EUT3.3 start crashing on new OS.
> I've double checked the crash - it turned out that I can't just start Eclipsse3.3 on SLES10 x86.
> To reproduce:
> 1. download eclipse-SDK-3.3-linux-gtk.tar.gz from http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500
> 2. unpack it, enter resulted 'eclipse' directory
> 3. run the command:
> time java -showversion -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -data ./workspace
> You'll get the stack dump of about 105-109 frames with the top like:
> SIGSEGV in VM code.
> Stack trace:
> 0: little2_nameLength (xmltok.c:-1)
> 1: MOZ_XML_GetBuffer (??:-1)
> 2: MOZ_XML_GetBuffer (??:-1)
> Could someone take a look? Moving to new platform (SLES9->SLES10) causes "regression" since M3 to be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4978) [drlvm][build][EUT] Eclipse3.3
crashes on SLES10 x86
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky updated HARMONY-4978:
---------------------------------------
Attachment: patch.patch
This is a suggested patch mostly based on windows export lists by the libraries. I didn't tough GC libraries yet. Patch undergoes testing. I would urge component owners to look at the export table by vmcode to check that all of the functions are actually required to be exported.
> [drlvm][build][EUT] Eclipse3.3 crashes on SLES10 x86
> ----------------------------------------------------
>
> Key: HARMONY-4978
> URL: https://issues.apache.org/jira/browse/HARMONY-4978
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Linux (SLES10) x86
> Reporter: Vladimir Beliaev
> Assignee: Gregory Shimansky
> Priority: Blocker
> Attachments: patch.patch
>
>
> Recent CC-based automated testing shows 4.45% pass rate for EUT3.3 on Linux x86:
> http://people.apache.org/~smishura/r585787/Linux_x86/eut33/
> This was caused by moving CC from SLES9 to SLES10 and EUT3.3 start crashing on new OS.
> I've double checked the crash - it turned out that I can't just start Eclipsse3.3 on SLES10 x86.
> To reproduce:
> 1. download eclipse-SDK-3.3-linux-gtk.tar.gz from http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500
> 2. unpack it, enter resulted 'eclipse' directory
> 3. run the command:
> time java -showversion -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -data ./workspace
> You'll get the stack dump of about 105-109 frames with the top like:
> SIGSEGV in VM code.
> Stack trace:
> 0: little2_nameLength (xmltok.c:-1)
> 1: MOZ_XML_GetBuffer (??:-1)
> 2: MOZ_XML_GetBuffer (??:-1)
> Could someone take a look? Moving to new platform (SLES9->SLES10) causes "regression" since M3 to be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-4978) [drlvm][build][EUT] Eclipse3.3
crashes on SLES10 x86
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-4978.
--------------------------------------
No response, assuming ok.
> [drlvm][build][EUT] Eclipse3.3 crashes on SLES10 x86
> ----------------------------------------------------
>
> Key: HARMONY-4978
> URL: https://issues.apache.org/jira/browse/HARMONY-4978
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Linux (SLES10) x86
> Reporter: Vladimir Beliaev
> Assignee: Gregory Shimansky
> Priority: Blocker
> Attachments: patch.patch
>
>
> Recent CC-based automated testing shows 4.45% pass rate for EUT3.3 on Linux x86:
> http://people.apache.org/~smishura/r585787/Linux_x86/eut33/
> This was caused by moving CC from SLES9 to SLES10 and EUT3.3 start crashing on new OS.
> I've double checked the crash - it turned out that I can't just start Eclipsse3.3 on SLES10 x86.
> To reproduce:
> 1. download eclipse-SDK-3.3-linux-gtk.tar.gz from http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500
> 2. unpack it, enter resulted 'eclipse' directory
> 3. run the command:
> time java -showversion -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -data ./workspace
> You'll get the stack dump of about 105-109 frames with the top like:
> SIGSEGV in VM code.
> Stack trace:
> 0: little2_nameLength (xmltok.c:-1)
> 1: MOZ_XML_GetBuffer (??:-1)
> 2: MOZ_XML_GetBuffer (??:-1)
> Could someone take a look? Moving to new platform (SLES9->SLES10) causes "regression" since M3 to be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-4978) [drlvm][build][EUT] Eclipse3.3
crashes on SLES10 x86
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536678 ]
Gregory Shimansky commented on HARMONY-4978:
--------------------------------------------
The reason for this bug is symbols conflict between DRLVM and mozilla-xulrunner package installed in SLES10. DRLVM contains APR which includes expat XML parser. Symbols of this library are exported since DRLVM exports all of its symbols. Mozilla XUL runner uses expat as well, but probably of different version. When eclipse starts up it runs some code from XUL runner in case it is installed, when this code runs XUL runner calls expat functions. But since DRLVM exports expat symbols, Mozilla calls DRLVM's version of expat. It leads to a crash because expat isn't of correct version that was used to compiled XUL runner.
The correct fix for this bug requires exporting only those symbols that are required for linking with JIT and GC and defining all other symbols from VM as local. As a workaround I removed mozilla-xulrunner package and eclipse started to work ok now. To remove mozilla-xulrunner package on SLES10 use
rpm -ev yelp mozilla-xulrunner
as root. Yelp is a gnome help browser and it is the only package that requires mozilla-xulrunner on SLES10.
> [drlvm][build][EUT] Eclipse3.3 crashes on SLES10 x86
> ----------------------------------------------------
>
> Key: HARMONY-4978
> URL: https://issues.apache.org/jira/browse/HARMONY-4978
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Linux (SLES10) x86
> Reporter: Vladimir Beliaev
> Assignee: Gregory Shimansky
> Priority: Blocker
>
> Recent CC-based automated testing shows 4.45% pass rate for EUT3.3 on Linux x86:
> http://people.apache.org/~smishura/r585787/Linux_x86/eut33/
> This was caused by moving CC from SLES9 to SLES10 and EUT3.3 start crashing on new OS.
> I've double checked the crash - it turned out that I can't just start Eclipsse3.3 on SLES10 x86.
> To reproduce:
> 1. download eclipse-SDK-3.3-linux-gtk.tar.gz from http://download.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500
> 2. unpack it, enter resulted 'eclipse' directory
> 3. run the command:
> time java -showversion -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar -data ./workspace
> You'll get the stack dump of about 105-109 frames with the top like:
> SIGSEGV in VM code.
> Stack trace:
> 0: little2_nameLength (xmltok.c:-1)
> 1: MOZ_XML_GetBuffer (??:-1)
> 2: MOZ_XML_GetBuffer (??:-1)
> Could someone take a look? Moving to new platform (SLES9->SLES10) causes "regression" since M3 to be fixed...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.