Problem with reading files used by other processes

[byates]

This was originally reported with SE20007 Beta but the problem still persists.  With 2007 I now get the "Error reading file" dialog box - not the stack trace.


----BETA ERROR REPORT-------

There has been some change with the file reading behavior between version 11 and the 2007 Beta.  With version 11 I am able to open and read log files that are being written by another process (a live application) with no problems.  SE reads up to the last data written and doesn't seem to try to read again until I switch the focus away from SE and back again.  I can search through the data and experience no file reading errors.  With the 2007 Beta I get multiple "Error Reading File" dialog boxes and sometimes a complete crash.  The file listed in the stack dump below was not even being written to at the time of the crash.  It was, however, still 'Opened' by the application doing the logging.  I verified that the same file could be read with no problems by SE11.

 Slick-C STACK TRACE ******************************
 Created on 2/25/2007 at 15:3:3 (718 ms)
 SlickEdit Version 12.0.0.0 Copyright 1988-2007 SlickEdit Inc.
 Edit module and type "st -f <offset>" to get the
 run-time error position

 error code=-33
 Error reading file

stdprocs.ex 6357 read_ahead()   p_window_id: 140   p_object: OI_FORM   p_name:
files.ex 2719 static(
   1:   -w +i:132 174 1129 662 N     "E:\Projects\Atlas\HW\FPGA\Modules\nexgen2_analysis\verif\scripts\LogFiles\nadi_digest_storage_csm2.log"
   2:   32
   3:   0
   p_window_id: 140
   p_object: OI_FORM
   p_name:
files.ex 390 edit(
   1:   -w +i:132 174 1129 662 N     "E:\Projects\Atlas\HW\FPGA\Modules\nexgen2_analysis\verif\scripts\LogFiles\nadi_digest_storage_csm2.log"
   2:   32
   3:   0
   p_window_id: 140
   p_object: OI_FORM
   p_name:
esdProjectExtensions.ex 2561 static(
   1:   BN="E:\Projects\Atlas\HW\FPGA\Modules\nexgen2_analysis\verif\scripts\LogFiles\nadi_digest_storage_csm2.log"
   2:   +i:132 174 1129 662 N
   3:   
   4:   <empty>
   5:   0
   p_window_id: 5
   p_object: OI_FORM
   p_name:
esdProjectExtensions.ex 1304 static(132 174 1129 662 -1 -1 N  WF=0 WT=3 "Default Fixed Font,12,0,1",
   2:   BN="E:\Projects\Atlas\HW\FPGA\Modules\nexgen2_analysis\verif\scripts\LogFiles\nadi_digest_storage_csm2.log"
   3:   LN=.143095 CL=4 LE=0 CX=4 CY=31 WI=127 BI=15 HT=0 HN=0 HF=0 HC=4
   4:   <empty>
   p_window_id: 5
   p_object: OI_FORM
   p_name:
esdProjectExtensions.ex 3698 static(3,230,<empty>)   p_window_id: 5   p_object: OI_FORM   p_name:
esdProjectExtensions.ex 131 _prjopen_esd_extension()   p_window_id: 5   p_object: OI_FORM   p_name:
files.ex 8196 call_list(_prjopen_)   p_window_id: 5   p_object: OI_FORM   p_name:
project.ex 953 _project_run_macro()   p_window_id: 5   p_object: OI_FORM   p_name:
main.ex 6881 defmain()   p_window_id: 5   p_object: OI_FORM   p_name:

[jbhurst]

Hi,

I've been seeing this too. I've used SlickEdit many times in the past to browse files while they are being written to, but now it seems it can't do it any more. I get a lot of "Error reading file" message boxes.

I don't think this is fixed yet.

Regards

John Hurst,
Wellington, New Zealand

[cconroy]

Hi,

I just upgraded to SE 2007 and am seeing the same behavior.  I was initially getting the stack dump too, but now only the message box.  Please count this as another vote for a quick fix; this is something I need to do every day!  (Also would be nice to have a way to refresh/reload said file from disk without closing and reopening -- but I'll settle for being able to use it in the same manner as previous versions.)

Thanks,
-Chris C.

[jayzee]

I have the same problem.

I run a Java program that creates an output file from within SE 2007 (Build->Execute) under Windows XP.

When I try to edit the output file using SE 2007, I get "Error reading file" dialog boxes. Sometimes I have to terminate SE 2007 from the Task Manager in Windows because the dialog box keeps reappearing before I can exit SE 2007.

I reinstalled SE 11.0.2 temporarily, and I do not have this problem with the prior version of SE.