Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When debugging on my Windows-7 64 bit VM machine I notice that sometimes (perhaps 50%) my exe name has been padded out with strange hex characters:
8000885a4fe0a0d0des.exe.11048
other times it is simply plain:
des.exe
These are 32 bit .Net4 assemblies built and run on a 64 bit system. As shown in TaskManager.
Anyone know why this is happening?
Edit: This is caused by Clearcase doing strange things on Windows-7. Why it randomly does this or how you can fix it I am not sure.
(I’m posting an answer based on the gist of the comments above, so the question stops showing up as “unanswered”.)
The problem seems to have been a confusing interaction between ClearCase and the Windows 7 Task Manager. Presumably the different hex-padded filenames represent different versions of the file from ClearCase revision control. Normally ClearCase hides this “nuts and bolts” stuff from the end-user, but in this case Task Manager is not fooled (or at least, only imperfectly fooled).