[Mono-bugs] [Bug 29853][Nor] Changed - mcs -g generates very large debugging files + warning

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
6 Sep 2002 12:22:33 -0000


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 martin@gnome.org.

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

--- shadow/29853	Tue Sep  3 23:42:45 2002
+++ shadow/29853.tmp.14910	Fri Sep  6 08:22:33 2002
@@ -1,14 +1,14 @@
 Bug#: 29853
 Product: Mono/MCS
 Version: unspecified
 OS: other
 OS Details: 
-Status: NEW   
+Status: ASSIGNED   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Misc
 AssignedTo: martin@gnome.org                            
 ReportedBy: miguel@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -35,6 +35,23 @@
 -rw-rw-r--    1 miguel   miguel   103079215164 Sep  3 23:39 mcs.dbg
 mono$ ls -l mcs.dbg
 -rw-rw-r--    1 miguel   miguel   103079215164 Sep  3 23:39 mcs.dbg
 mono$ du mcs.dbg
 276
 mcs.dbg
+
+------- Additional Comments From martin@gnome.org  2002-09-06 08:22 -------
+Hmm, this is very weird - epecially since 0xc is not a valid value for SeekOrigin.
+
+However, this may be a "bootstrapping issue".  Try the following:
+
+* remove the old Mono.CSharp.Debugger.dll
+
+* recompile and install the class libs, including Mono.CSharp.Debugger
+
+* compile a new mcs _without_ debugging.
+
+* try compiling mcs with debugging with the newly compiled mcs.
+
+Your old mcs won't be able to use the new symbol writer and vice-versa, but you _should_ get an exception in this case.
+
+