[K42-discussion] crash in FileSystemGlobal::FSFileGlobal::rename

[Dilma DaSilva]

I can't reproduce the bug by just removing a file and then renaming
it. The scenario is probably more complicated.

It's perfect legal to call rename with the last argument renamedFinfo
NULL. And the FIXMEs on the DirLinuxFS::rename code are not about
non-existent files, but files not currently being cached.

It seems in order to pursue this I should try running AIM7 here.

dilma

 > 
 > Here's a fairly complete backtrace for a crash in baseServers when a process 
 > removes and then tries to move a nonexistent file. I'm not sure why the 
 > configure script is doing that, but hopefully the backtrace below is complete 
 > enough for someone more familiar with the FS code to spot the bug (rename 
 > being called with renamedFinfo = NULL). There are certainly a lot of FIXMEs 
 > about nonexistent files around that code (DirLinuxFS::rename).
 >