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
Yes, you should be able to use SOS in FreeBSD.
The doc docs\debugging\sos.html explains how to use SOS in UNIX platform.
As for who calls GcHEap::Alloc, why don't you set a bp on it and then run your program?
-Original Message-
From: Discussion of the Rotor Shared Source CLI
SOS does work on FreeBSD - you invoke it differently than you do on Windows though.
From the GDB prompt, switch to thread #5 and type:
call SOS(DumpStack)
that is equivalent to doing this in NTSD:
!sos.DumpStack
To find the start of the jitted function, disassemble backwards
The implementation for BeginInvoke and EndInvoke comes from
COMDelegate::GetInvokeMethodStub (clr\src\vm\prestub.cpp).
The actual code is emitted in CTPMethodTable::CreateDelegateStub
(clr\src\VM\i386\remotingx86.cpp).
-Jan
-Original Message-
From: Discussion of the Rotor Shared Source
Hi,
i checked the environment vars, they are all set right, but gdb complains
about DumpStack?
do i have anything extra to make it work?
(gdb) call SOS(DumpStack)
SOS: Command 'DumpStack' not found.
thanks
archana
On Wed, 7 Jul 2004, Barry Bond wrote:
SOS does work on FreeBSD - you invoke
Unfortunately, we did not have enough time to implement DumpStack on FreeBSD. The
workaround is to use a regular backtrace, and then use IP2MD SOS command to get the
names for managed methods.
Below is transcript of debugging session that demonstrates it.
-Jan
(gdb) break main
Breakpoint 1 at
Thank you so much!
On Wed, 7 Jul 2004, Jan Kotas wrote:
Unfortunately, we did not have enough time to implement DumpStack on FreeBSD. The
workaround is to use a regular backtrace, and then use IP2MD SOS command to get the
names for managed methods.
Below is transcript of debugging session
