If you can reproduce the problem while capturing OpenAFS Trace output it would help to track down the problem. In particular I need to identify which routines were used to create the temporary file. It looks like a counted string is being used as a nul terminated string at some point.
Charles Karney wrote: > I recently upgraded my Windows XP machine from OpenAFS 1.5.32 to 1.5.51 > and then to 1.5.52. With both versions, 1.5.5x, when I do compilations > under Visual Studio 2003, I get error messages of the form: > > Compiling... > cl : Command line error D2022 : cannot open > 'u:\win\proj\src\latlongutmconversionlib\Release\RSP000033.rsp' > Could not delete temporary file. Make sure that you do not have it > open and that the file is not protected. > > If I list the Release directory on a Linux box, I see that rsp file has > some trailing junk characters (from find -ls) > > 37450452 1 -rwxrwxrwx 1 ckarney ckarney 157 Aug 20 15:35 > ./Release/RSP000033.rsp\001\350\200\204 > > Downgrading back to 1.5.32 gets rid of this problem. > > Perhaps this is some bug that's triggered by OpenAFS's support of > Unicode filenames? >
smime.p7s
Description: S/MIME Cryptographic Signature
