[Mono-bugs] [Bug 60613][Maj] Changed - NullReferenceException in OracleDataReader.GetSchemaTable caused by JIT optimizations

[bugzilla-daemon@bugzilla.ximian.com]

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 lupus@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=60613

--- shadow/60613	2004-06-25 10:09:23.000000000 -0400
+++ shadow/60613.tmp.9285	2004-06-25 10:30:44.000000000 -0400
@@ -232,6 +232,21 @@
 After stopping execution at that point and printing the value as you
 requested I get the value 135199392. My Console.WriteLine gave me
 135912880 for ErrorHandle before. So it's not the right offset or the
 value has changed.
 
 I'm a little bit lost here as I'm not a gdb expert.
+
+------- Additional Comments From lupus@ximian.com  2004-06-25 10:30 -------
+Ok, thanks, I know this is painful: was the WriteLine you mention from
+the same session?
+Some other useful info: comment the WriteLines
+and attach the output of running mono --trace ...
+(it's enough just the stuff from GetSchemaTable() and later).
+If possible it would be useful to know if mono 0.91 works
+when running with mono -O=loop to check if it's a bad interaction of
+the loop optimization with the register allocator or some other change
+introduced later. If you could try a few intermediate builds of mono
+from a time where it worked to when it started failing it might help
+pinpoint the issue.
+Otherwise we'll have to disbale -O=loop from the default optimization
+set for the release.