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=78782 --- shadow/78782 2006-07-06 17:57:52.000000000 -0400 +++ shadow/78782.tmp.7334 2006-07-07 06:21:29.000000000 -0400 @@ -1,22 +1,22 @@ Bug#: 78782 Product: Mono: Runtime Version: 1.1 -OS: +OS: unknown OS Details: Status: NEW Resolution: -Severity: +Severity: Unknown Priority: Blocker Component: JIT AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: -Cc: +Cc: [EMAIL PROTECTED],[EMAIL PROTECTED] Summary: Segfault on PPC when using a libgcc_s/libpthread compiled with SSP Description of Problem: @@ -312,6 +312,16 @@ Bye PS: this really only happens on PPC, all other archs work fine. And everything non-mono works fine on PPC too ;) And this is now with all kinds of PPC, not only PPC64 with 32 bit userland. + +------- Additional Comments From [EMAIL PROTECTED] 2006-07-07 06:21 ------- +This is all on a PPC32 btw... and when running mono with g_malloc() in +the places with gdb one gets the same backtrace as I've written at the +end so we have 2 bugs here: +1) the segfault somewhere in the unwinding code which is most probably +caused by mono because it does weird things (maybe something with +stack alignement? but this is only a wild guess) +2) the segfault in the segfault handler of mono which can be fixed by +using the codemanager instead of g_malloc() for some reason. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
