Most Likely Reason for a Crash

J

Jay1b

Well-known member
Joined
Aug 3, 2003
Messages
640
Location
Kent, Uk.
Hi, i got the following message on very well tested system earlier today, i have ever encounted the message before. From looking at it, it would appear that the file become to big to handle - but the files in question are all considerably smaller then ones previously opened by the same program. Has anyone got a better observation of the message below?

Thanks.
Jay

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: IO operation will not work. Most likely the file will become too long or the handle was not opened to support synchronous IO operations.
at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.FileStream.FlushWrite()
at System.IO.FileStream.Flush()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Dispose(Boolean disposing)
at System.IO.StreamWriter.Close()
at RoverComPort.modReadBuffer.WriteToFile(String& strcurrentline, String Path, Boolean ErrOk, String MsgType)
at RoverComPort.modReadBuffer.ReadBuffer()
at RoverComPort.frmRoverBMain.tmrReadCommBuffer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.Callback(IntPtr hWnd, Int32 msg, IntPtr idEvent, IntPtr dwTime)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
RoverComPort
Assembly Version: 1.7.0.25642
Win32 Version: 1.7.0.25642
CodeBase: file:///D:/Rover%20Com%20Port%20Monitor/RoverComPort.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
AxInterop.MSCommLib
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///D:/Rover%20Com%20Port%20Monitor/AxInterop.MSCommLib.DLL
----------------------------------------
AxInterop.MSFlexGridLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Rover%20Com%20Port%20Monitor/AxInterop.MSFlexGridLib.DLL
----------------------------------------
Interop.MSCommLib
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///D:/Rover%20Com%20Port%20Monitor/Interop.MSCommLib.DLL
----------------------------------------
Interop.MSFlexGridLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Rover%20Com%20Port%20Monitor/Interop.MSFlexGridLib.DLL
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.3052.4
CodeBase: file:///c:/winnt/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
 
Is it possible that the file was

1. Locked by another process?
2. Not closed/ in use from the last process?
3. Read only?

Just a couple of ideas.
 
Thanks, but it crashed whilst creating a new file, so i dont think any of them would apply. So the file became to long to handle would probably have to be it. But as i said earlier, the file is smally then previous files that were handled fine.
 
Found the problem. Some idiot slightly changed the name of the directory the files get written too. So the program was trying to write to a directory that doesnt exist anymore.
 
if (Directory.Exists(...) ) should be used when you dont know if something does exist..
 
Back
Top