[Mono-bugs] [Bug 78597][Nor] Changed - NRE in SSL/NPGSQL

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Jun 7 09:03:59 EDT 2006

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 sebastien at ximian.com.


--- shadow/78597	2006-06-07 07:25:32.000000000 -0400
+++ shadow/78597.tmp.29432	2006-06-07 09:03:59.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 78597
 Product: Mono: Class Libraries
-Version: 1.0
+Version: 1.1
+OS: Windows XP
 OS Details: 
-Status: NEW   
+Status: NEEDINFO   
-Priority: Major
+Severity: Unknown
+Priority: Normal
 Component: Mono.Security
 AssignedTo: sebastien at ximian.com                            
 ReportedBy: mfarr at paradise.net.nz               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
-Summary: Object reference not set to an instance of an object
+Summary: NRE in SSL/NPGSQL
 Description of Problem:
 "Object reference not set to an instance of an object." in
 Mono.Security.dll when loading large amounts of data with ssl+npgsql.
 Steps to reproduce the problem:
@@ -55,6 +55,42 @@
        at Mono.Security.Protocol.Tls.SslStreamBase.Read(Byte[] buffer,
 Int32 offset, Int32 count)
        at System.IO.BufferedStream.ReadByte()
        at Npgsql.NpgsqlState.ProcessBackendResponses_Ver_3(NpgsqlConnector
 context) in D:\csharpd\Npgsql1.0RC1-src\Npgsql\Npgsql\NpgsqlState.cs:line 463
+------- Additional Comments From sebastien at ximian.com  2006-06-07 09:03 -------
+You're lucky to have a 100% predictable test case but yours is too
+complex to replicate here (and I'm not sure it would fail as it's
+predictability may be related to the extact size, OS...). I'll
+probably need to supply you "special builds" to isolate the problem
+but before that I need more information.
+From your report it looks like you are running the client on the MS
+runtime 2.0 (on Windows). This is probably the least tested
+configuration to use Mono.Security.dll so I'll need more information
+to isolate the problem.
+? is the Npgsql server running on Windows too ?
+? does this works without using SSL ?
+? did you check for other Mono.Security.dll outside the GAC ?
+? did you look into all GACs, i.e. 1.0/1.1/2.0 ?
+Things to try:
+- Compile Mono.Security.dll with VS.NET 2005 so you'll get the
+debugging information (including the extact line where the NRE
+occurs). If you have issues doing so then we should fix that first;
+- Compile your application (or part of it) and dependencies
+(Mono.Security and Npgsql) with .NET 1.1 and see if the same error
+occurs. 2.0 isn't much tested and it's possible that something changed
+between SSL and NPGSQL (like in the BufferedStream between them);
+- Execute your application (or test case) on Mono (at least on Windows
+and if possible on Linux) for both the 2.0 and the 1.1 profile - if it
+works then it would indicate that the code depends on a Mono-specific

More information about the mono-bugs mailing list