Fwd: 7.5nc stability under Leopard (Mac OSX 10.5.2)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Fwd: 7.5nc stability under Leopard (Mac OSX 10.5.2)

Pavel Perikov

On 20.02.2008, at 20:54, Alan Knight wrote:
There has been a great deal of work on the MacOSX VM for 7.6, which is currently in release candidates, and so should ship shortly. So, yes.


That's great news! Hope it will be ready soon. Right now i doomed to get the following:

Thread 1 Crashed:
0   com.cincom.vw7.5               0x00032e72 incMarkLoop + 252 (mmIncGC.c:1204)
1   com.cincom.vw7.5               0x00033575 incMarkSweep + 1041 (mmIncGC.c:1038)
2   com.cincom.vw7.5               0x00033875 incGCPrim + 294 (mmIncGC.c:542)
3   com.cincom.vw7.5               0x00054e63 rtPrimGlueMany2 + 3

Reply | Threaded
Open this post in threaded view
|

Re: 7.5nc stability under Leopard (Mac OSX 10.5.2)

Eliot Miranda-2


On Wed, Feb 20, 2008 at 6:33 PM, Pavel Perikov <[hidden email]> wrote:

On 20.02.2008, at 20:54, Alan Knight wrote:
There has been a great deal of work on the MacOSX VM for 7.6, which is currently in release candidates, and so should ship shortly. So, yes.


That's great news! Hope it will be ready soon. Right now i doomed to get the following:

Thread 1 Crashed:
0   com.cincom.vw7.5               0x00032e72 incMarkLoop + 252 (mmIncGC.c:1204)
1   com.cincom.vw7.5               0x00033575 incMarkSweep + 1041 (mmIncGC.c:1038)
2   com.cincom.vw7.5               0x00033875 incGCPrim + 294 (mmIncGC.c:542)
3   com.cincom.vw7.5               0x00054e63 rtPrimGlueMany2 + 3


Looks like heap corruption.  Are you doing heavy DLLCC work?  Are you sure the heap isn't getting corrupted?  Cincom can tell you how to run an assert or debug VM to check the heap...
Reply | Threaded
Open this post in threaded view
|

Re: 7.5nc stability under Leopard (Mac OSX 10.5.2)

Pavel Perikov
>>
>
> Looks like heap corruption.  Are you doing heavy DLLCC work?  Are  
> you sure the heap isn't getting corrupted?  Cincom can tell you how  
> to run an assert or debug VM to check the heap...

It looks so to me too. Something is definitely wrong with object  
memory.  I'm not doing any DLLCC work nor i have DLLCC package in my  
image. I'll give a try to assert VM. Eliot, thank you for suggestion.

Pavel