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=81685 --- shadow/81685 2007-05-19 13:26:07.000000000 -0400 +++ shadow/81685.tmp.17597 2007-05-20 08:55:05.000000000 -0400 @@ -1,14 +1,14 @@ Bug#: 81685 Product: Mono: Runtime Version: 1.2 -OS: +OS: unknown OS Details: Status: NEW Resolution: -Severity: +Severity: Unknown Priority: Wishlist Component: JIT AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- @@ -25,6 +25,17 @@ sigaltstack stack with the GC is a possibility, but would slow down the GC as a big blog of mostly unused memory would be registered. The open sourced Java VM does not seem to be using sigaltstack to detect this case, they seem to use another setup to detect overflows, it might be worth investigating this. + +------- Additional Comments From [EMAIL PROTECTED] 2007-05-20 08:55 ------- +According to this: + +http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/crashes.html + +HotSpot does this by adding checks to compiled java code, most likely +by touching a memory location a couple of pages down the stack in the +method prolog. This could work for us, but it would slow down every +method call + localloc. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
