You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "George Timoshenko (JIRA)" <ji...@apache.org> on 2007/04/13 13:41:15 UTC
[jira] Created: (HARMONY-3649) [drlvm] SPECjbb2005 intermittently
fails on EM64T in server mode
[drlvm] SPECjbb2005 intermittently fails on EM64T in server mode
----------------------------------------------------------------
Key: HARMONY-3649
URL: https://issues.apache.org/jira/browse/HARMONY-3649
Project: Harmony
Issue Type: Bug
Components: DRLVM
Environment: EM64T
Reporter: George Timoshenko
Attachments: stack
The failure is very unstable.
You can get only 1 failure from 10 runs.
Or see 3 failures in a row.
The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov resolved HARMONY-3649.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.0M4
Applied the enhanced patch at revision: 600836.
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Assignee: Alexey Varlamov
> Fix For: 5.0M4
>
> Attachments: H3649.patch, H3649.patch, stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Evgueni Brevnov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgueni Brevnov updated HARMONY-3649:
-------------------------------------
Attachment: H3649.patch
As you can see from stack trace we have a problem with memory allocation by default STL allocator. On Windows default STL allocator just delegates to system malloc/new. On Linux there is internal STL implementation which may potentially have bugs, etc. More over it's really strange to have __simple_alloc::alloc on the stack since this is thread unsafe version of standart allocator. To get rid of above problems I changed the code to use Jitrino internal allocator. Doing so allows to be protected against multi-threading issues and STL bugs.
With that patch SpecJBB2005 didn't crashed over the night run. Build test checked on Lin ia32/em64t.
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Attachments: H3649.patch, stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky updated HARMONY-3649:
---------------------------------------
Summary: [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode (was: [drlvm] SPECjbb2005 intermittently fails on EM64T in server mode)
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Attachments: stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov reassigned HARMONY-3649:
----------------------------------------
Assignee: Alexey Varlamov
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Assignee: Alexey Varlamov
> Attachments: H3649.patch, stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548157 ]
Alexey Varlamov commented on HARMONY-3649:
------------------------------------------
Evgueni, nice catch!
I just wonder why you kept copying of the UseSets instead of using references - apparent waste of resources here.
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Assignee: Alexey Varlamov
> Attachments: H3649.patch, H3649.patch, stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3649) [drlvm] SPECjbb2005 intermittently
fails on EM64T in server mode
Posted by "George Timoshenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Timoshenko updated HARMONY-3649:
---------------------------------------
Attachment: stack
example of call stack
> [drlvm] SPECjbb2005 intermittently fails on EM64T in server mode
> ----------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Attachments: stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Evgueni Brevnov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546109 ]
Evgueni Brevnov commented on HARMONY-3649:
------------------------------------------
I'm able to reproduce this problem on latest sources (November 28'07).
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Attachments: stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3649) [drlvm][jit] SPECjbb2005
intermittently fails on EM64T in server mode
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov updated HARMONY-3649:
-------------------------------------
Attachment: H3649.patch
Updated the fix accordingly.
> [drlvm][jit] SPECjbb2005 intermittently fails on EM64T in server mode
> ---------------------------------------------------------------------
>
> Key: HARMONY-3649
> URL: https://issues.apache.org/jira/browse/HARMONY-3649
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: EM64T
> Reporter: George Timoshenko
> Assignee: Alexey Varlamov
> Attachments: H3649.patch, H3649.patch, stack
>
>
> The failure is very unstable.
> You can get only 1 failure from 10 runs.
> Or see 3 failures in a row.
> The failure allways looks like a segfault when some new object is being allocated in STL code. (iterator, new item in a container, just a new std::string...)
> Usually the STL code is being called from execution manager or Jitrino.OPT code. But the caller's code is OK and does not give any clue.
> the first time the failure was observed is April 4.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.