Subject: | filenames should be shortened if necessary |
I was trying to profile some code that exists on a fairly lengthy NFS
directory path. My include path had short symlinks to that path so
NYTProf's attempt to strip off the INC prefix were unsuccessful. This
resulted in a filename that was too long for the filesystem (ext3) to
handle.
I'm not sure if the filenames are supposed to be easily recognizable but
I would suggest that if it's too long (i.e. > 255 characters) that some
sort of shortening be applied before trying to write the file. Perhaps
using an MD5 hash to ensure uniqueness or something?
I ended up hard-coding the canonical path into the path prefix stripping
code to get it to work but I'd hope this is a (probably rare) corner
case that NYTProf could handle.
Thanks!