[M3devel] CM3 d5.5.0 CVSup client issues.

[Tony Hosking]

Hmm...

What output do you get with "cm3cg --version"?  On my machine I see:

/p/sss/cm3/bin/cm3cg --version
Modula-3 backend version 4.1.1 (sparc-sun-solaris2.8)
         compiled by GNU C version 4.1.1.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min- 
heapsize=131072

On Sep 7, 2007, at 1:51 PM, Alex Bochannek wrote:

> Tony Hosking <hosking at cs.purdue.edu> writes:
>
>> Sounds like we are losing some references somewhere and the GC is
>> prematurely collecting live objects.  Alex, are you running on a 64-
>> bit SPARC v9?  Perhaps the SaveRegsInStack code needs updating for
>
> Yes.
>
> -bash-3.00$ isainfo -kv; isainfo -v
> 64-bit sparcv9 kernel modules
> 64-bit sparcv9 applications
>         vis2 vis
> 32-bit sparc applications
>         vis2 vis v8plus div32 mul32
>
>> that platform to use the flushw instruction instead of trap 3.  As it
>> is, I am not entirely satisfied with the difficulties I've seen
>> getting meaningful stack information on Solaris for stopped threads,
>> but without a reliable way to diagnose the problem I don't know what
>> to do from this end.  See additional comments below:
>
>>> With the nogc options cvsup pretty much always runs all the way to
>>> completion. It takes a while, especially on an existing tree, but it
>>> will complete without problems.
>>
>> When you say "pretty much" what do you mean?  Does it sometimes  
>> get an
>> error?  Is it the one you note above?
>
> I should have been more precise here. Every time I ran cvsup with
> @M3nogc and I let it run to completion, it completed without
> error. Since it took a while, I did interrupt it a few times during
> testing.
>
> Alex.