Why are process image names sometimes padded with hexadecimal characters?

When debugging a VM with Windows-7 on my 64-bit machine, I notice that sometimes (maybe 50%) my exe name was supplemented with strange hexadecimal characters:

8000885a4fe0a0d0des.exe. 11048

in other cases it is simple:

des.exe

These are 32-bit .Net4 assemblies created and run on a 64-bit system. As shown in TaskManager.

Does anyone know why this is happening?

Edit: this is because Clearcase does strange things on Windows 7. Why it accidentally does this or how you can fix it, I'm not sure.

+8
debugging windows-7 clearcase windows-7-x64
source share
1 answer

(I am posting an answer based on the nature of the comments above, so the question is no longer displayed as “no answer.”)

The problem seemed to be the confusing interaction between ClearCase and the Windows 7 task manager. Presumably, the different hexadecimal file names are different versions of the file from ClearCase version control. ClearCase usually hides these “nuts and bolts” from the end user, but in this case the task manager is not tricked (or at least only imperfectly fooled).

+2
source share

All Articles