Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75725 --- shadow/75725 2005-08-05 14:33:57.000000000 -0400 +++ shadow/75725.tmp.25353 2005-08-05 14:33:57.000000000 -0400 @@ -0,0 +1,55 @@ +Bug#: 75725 +Product: Mono: Runtime +Version: 1.1 +OS: Solaris 8 +OS Details: SPARC +Status: NEW +Resolution: +Severity: +Priority: Blocker +Component: debug +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: bug in mono_debug_add_type + +Please fill in this template when reporting a bug, unless you know what you +are doing. +Description of Problem: +mono_debug_add_type with 1.1.8.2 core dumps because it attempts to assign a +pointer to a non-long word boundary. + +Steps to reproduce the problem: +1. make check +2. +3. + +Actual Results: +Core dumps after several tests + +Expected Results: +Not to core dump. + +How often does this happen? +Always + +Additional Information: +The issue with mono_debugger_add_type is with the following lines (from +memory, since I am on a different machine): + +write_leb(...); +write_leb(...); +write_leb(...); +* ((gpointer*) ptr) = klass; + +Write_leb can move the pointer to an offset that is not on a pointer +boundary and the SPARC architecture does not allow a pointer to be written +on an odd boundary (or word boundaries that are not also long boundaries, +ie pointer % 4 != 0...actually, it probably even pointer % 8 != 0 for 64- +bit). I've change the code to behave as though they were two guint8* +(which is convenient, since one is defined that way) and loop through the +data. I do not know what the data is used for, I am unsure that that is +appropriate. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
