>
>
> -Original Message-
> From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL
> PROTECTED] On Behalf Of Archana
> Sent: Wednesday, July 07, 2004 9:07 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET-ROTOR] tracking the source of an alloc
cussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL
PROTECTED] On Behalf Of Archana
Sent: Wednesday, July 07, 2004 9:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET-ROTOR] tracking the source of an alloc
Hi,
i checked the environment vars, they are all set right, but gdb complains
a
you do find it.
>
> Barry
>
> -Original Message-
> From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL
> PROTECTED] On Behalf Of Archana
> Sent: Wednesday, July 07, 2004 9:03 AM
> To: [EMAIL PROTECTED]
> Subject: [DOTNET-ROTOR] tracking the so
om: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL
PROTECTED] On Behalf Of Archana
Sent: Wednesday, July 07, 2004 9:03 AM
To: [EMAIL PROTECTED]
Subject: [DOTNET-ROTOR] tracking the source of an alloc
Hi,
How can one find out where the call to GcHEap::Alloc is
originatin
e CLI implementation [mailto:[EMAIL
PROTECTED] On Behalf Of Archana
Sent: Wednesday, July 07, 2004 9:03 AM
To: [EMAIL PROTECTED]
Subject: [DOTNET-ROTOR] tracking the source of an alloc
Hi,
How can one find out where the call to GcHEap::Alloc is
originating from?
i had sent a similar mail regarding how to deb
Hi,
How can one find out where the call to GcHEap::Alloc is
originating from?
i had sent a similar mail regarding how to debug in
such cases long time back (ref:help needed wrt debugging, Jul24,2003,
that Barry Bond helped me with). i tried the method that was
suggested. but i am not able to locat
