[Mono-bugs] [Bug 78775][Nor] New - Mono run with -v -v always uses the same temp files and doesn't clean them up when done

[bugzilla-daemon at 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 seurer at us.ibm.com.

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

--- shadow/78775	2006-07-06 13:02:12.000000000 -0400
+++ shadow/78775.tmp.24546	2006-07-06 13:02:12.000000000 -0400
@@ -0,0 +1,53 @@
+Bug#: 78775
+Product: Mono: Runtime
+Version: 1.1
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: JIT
+AssignedTo: lupus at ximian.com                            
+ReportedBy: seurer at us.ibm.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Mono run with -v -v always uses the same temp files and doesn't clean them up when done
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+In mono_disassemble_code in helpers.c it always writes the intermediate
+files it creates for the disassembly (caused by running mono with -v -v)
+into /tmp/test.s and /tmp/test.o (on Linux anyway, looks similar for other
+OSes).  It also does not erase these files when it is done.  This is fine
+for a single user system but when several people are doing this on the same
+system this can cause two problems.  First if the users on the system do
+not have root/god/whatever authority only one person can disassemble code
+ever because the other people will not be able to overwrite the files left
+behind by the first person.  If one person runs several instances of mono
+with -v -v at once or multiple different people run it at the same time the
+files in /tmp will be overwritten by the others.  We noticed this with
+mono-1.1.15 on both Linux and AIX.
+
+
+Steps to reproduce the problem:
+1. Run a program using verbose level 2 (i.e., mono -v -v whatever.exe)
+2. Look in the temp directory (/tmp on Linux) and you will see the temp
+files still there.
+
+Actual Results:
+The disassembly on the JITted code always uses /tmp/test.s and /tmp/test.o
+(on Linux for example) and doesn't erase them when it is done.
+
+Expected Results:
+The disassembly should use a unique name for each one (by using the tmpnam
+C function for instance) and should erase the files when it is done.
+
+How often does this happen? 
+- Every time
+
+
+Additional Information: