Bug 316274 (MONO68572) - Method signature mismatch between debugger and JIT
Summary: Method signature mismatch between debugger and JIT
Status: RESOLVED FIXED
Alias: MONO68572
Product: Mono: Debugger
Classification: Mono
Component: backend (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Major
Target Milestone: ---
Assignee: Chris Toshok
QA Contact: Martin Baulig
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-20 08:59 UTC by Martin Baulig
Modified: 2007-09-15 21:24 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wiest 2007-09-15 18:56:43 UTC


---- Reported by martin@ximian.com 2004-10-20 01:59:55 MST ----

When the debugger triggers a JIT compilation, there's a mismatch between
the method signature the debugger generates and the one the JIT expects.

The code which checks the signature in the JIT is in
mono_signature_get_desc() in mono/metadata/debug-helpers.c.

The debugger creates this signature in
MonoSymbolFile.MonoMethod.RegisterLoadHandler() in
backends/mono-csharp/MonoCSharpLanguageBackend.cs

These signatures must be the same, so we either need to modify the code in
the debugger or the one in the JIT - I'm not sure what's the right place. 
Maybe we should have a look at which kinds of signatures the JIT expects
and thing about whether it makes sense to make some changes there.



---- Additional Comments From martin@ximian.com 2004-10-20 02:00:40 MST ----

Chris, could you have a look at this ?



---- Additional Comments From martin@ximian.com 2004-10-20 02:01:31 MST ----

Btw. this caused the `b Console.WriteLine (bool)' hang.



---- Additional Comments From toshok@ximian.com 2005-04-19 18:42:32 MST ----

this has been fixed for ages.  marking it so.


Unknown operating system unknown. Setting to default OS "Other".