[Mono-bugs] [Bug 325261] Profiling xsp/xsp2 (requesting an empty .aspx) always leads to crash

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=325261#c1





--- Comment #1 from Massimiliano Mantione <massi at ximian.com>  2007-11-05 15:48:29 MST ---
This *seems* to be related to freeing portions of metadata before printing the
profiler results.

I isolated the crash inside "method_get_name" in "profiler.c".
It happens when printing the callers of
"System.Web.HttpUtility::runtime_invoke_void(object,intptr,intptr,intptr)",
particularly when printing the name "ASP.index_aspx::.ctor()".

At that point, none of the pointers is NULL, but it *seems* that
"method->klass->name_space" points to an invalid address, or something
like that, in any case the sigsegv happens in the g_strdup_printf, but
none of its arguments is NULL.

I cannot reproduce this in gdb, so I resorted to printf, I know the
exact method because I also printed the MonoMethod* values at jit time.

None of my attempts to print the results earlier gave good results
so far... anyway, the new (logging) profiler is not affected by this
problem.
And this bug is does not seem a regression, at least it has not been
caused by my addition of profiler hooks because it predates them.

Should I *really* insist in fixing the old profiler, which in this
case (xsp, many dynamic things) is flawed by design, or should I just
move on to the new profiler?


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.