6:51 AM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET-ROTOR] about Pinning objects
Hi,
On Thu, 5 Feb 2004, Jan Kotas wrote:
> If both foo and bar are on the stack the callback will be called
> multiple times for the string: for the argument of foo(), for the
> argument of bar() and finally for
Hi,
On Thu, 5 Feb 2004, Jan Kotas wrote:
> If both foo and bar are on the stack the callback will be called
> multiple times for the string: for the argument of foo(), for the
> argument of bar() and finally for the pinned variable in bar(). Only the
> very last one is going to have the pinned bi
I implementation
[mailto:[EMAIL PROTECTED] On Behalf Of Archana
Sent: Thursday, February 05, 2004 6:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET-ROTOR] about Pinning objects
Hi,
On Thu, 5 Feb 2004, Jan Kotas wrote:
> The only way to see in the current implementation whether the given
>
Hi,
On Thu, 5 Feb 2004, Jan Kotas wrote:
> The only way to see in the current implementation whether the given
> object is pinned is by scanning all GC roots. The GC_CALL_PINNED flag is
> going to be set in the callback for objects that are pinned.
>
You are referring to the Promote(..) call wher
Source CLI implementation
[mailto:[EMAIL PROTECTED] On Behalf Of Archana
Sent: Thursday, February 05, 2004 5:54 AM
To: [EMAIL PROTECTED]
Subject: [DOTNET-ROTOR] about Pinning objects
Hi,
Is there someway to find out that - 'a certain object
X is no longer pinned' ?
For instance in the test pr
Hi,
Is there someway to find out that - 'a certain object
X is no longer pinned' ?
For instance in the test program
sscli/tests/gc/methodical/pinning/pinningother/pinnedcollect.exe,
a handle(handle1) is created to pin 'arr'. this causes the pin bit
to be set for object arr. But the rotor GC mecha
