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=78140 --- shadow/78140 2006-04-20 04:13:56.000000000 -0400 +++ shadow/78140.tmp.17626 2006-04-20 08:21:05.000000000 -0400 @@ -1,13 +1,13 @@ Bug#: 78140 Product: Mono: Class Libraries Version: 1.1 OS: unknown OS Details: W2k -Status: REOPENED -Resolution: +Status: RESOLVED +Resolution: NOTXIMIAN Severity: Unknown Priority: Normal Component: Mono.Security AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -249,6 +249,23 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-04-20 04:13 ------- Could you attach the debug version of Mono.Security please? I solved this bug but now i get another one. (Probably too in Indy.Sockets, but Mono.Security slicks exceptions) + +------- Additional Comments From [EMAIL PROTECTED] 2006-04-20 08:21 ------- +I could, but the debug info wouldn't help you unless : + +* you are running under the Mono runtime (.mdb debug files); + +* the debugging messages I added are only where the original exception +happened. So it's very likely they wouldn't help you. + +That being said, it would seem that Mono reports better (more +accurate) stack trace than MS in this case. You may want to execute +your code under Mono to see if it helps. + + +P.S. please do not re-open this bug unless the original problem finds +it's way back into Mono ;-). Note that you can still add details to +the closed bug and I'll still receive email notification about them. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
