[Mono-bugs] [Bug 59934][Maj] New - ILASM does not recognize C style end of line comments

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 10 Jun 2004 06:13:01 -0400 (EDT)


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 infodate@aster.pl.

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

--- shadow/59934	2004-06-10 06:13:01.000000000 -0400
+++ shadow/59934.tmp.15096	2004-06-10 06:13:01.000000000 -0400
@@ -0,0 +1,58 @@
+Bug#: 59934
+Product: Mono: Compilers
+Version: unspecified
+OS: 
+OS Details: Win XP SP1 PL
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: IL assembler
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: infodate@aster.pl               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: ILASM does not recognize C style end of line comments
+
+Description of Problem:
+
+ILASM incorrectly recognizes C style line end comments proceded with "//" 
+throwing exception.
+
+
+Steps to reproduce the problem:
+
+1. Disassemble system.design.dll (.NET) with MS ildasm or mono ildasm.
+2. Remove white space in front of byte blob of first assembly custom 
+attribute entry to account for another bug - white space misrecegnotion in 
+front of byte blobs.
+2. Reassemble using ilasm
+
+Actual Results:
+
+Assembling 'system.design.il' , no listing file, to dll --
+> 'system.design.dll'
+Error at: line (54) column (146)
+System.Exception: Invalid hex value. '/'.
+in <0x0014e> Mono.ILASM.ILTokenizer:GetNextToken ()
+in <0x00011> Mono.ILASM.ILTokenizer:get_NextToken ()
+in <0x00017> Mono.ILASM.ScannerAdapter:advance ()
+in <0x007c0> Mono.ILASM.ILParser:yyparse (Mono.ILASM.yyParser.yyInput)
+in <0x000ca> Mono.ILASM.ILParser:yyparse 
+(Mono.ILASM.yyParser.yyInput,object)
+in <0x00216> DriverMain:ProcessFile (string)
+
+Expected Results:
+
+File should be compiled into .dll and in the process all comments should 
+be accounted for and ommitted.
+
+
+How often does this happen? 
+
+Everytime test is run.
+
+
+Additional Information: