Incorrect PID formatting?

[JKWood]

I was attempting to use winedbg to attach to a misbehaving Windows executable thread, when much to my surprise it spit out a different PID than the one I put in (in this case, it was telling me I couldn't attach to that PID.)

After digging in the source for winedbg, I discovered that it uses the %04x hexadecimal formatting string for displaying pretty much any piece of information in any debug message, and specifically in the "could not attach to" message (stack.c, line 419 in the current git). So, we have a program that accepts decimal PIDs as arguments, but spits out the hexadecimal version in output messages.

The thing is, the printf formatting string doesn't affect the data itself, so I can't really see a valid reason for not returning the format users should expect. However, I'm always open to being told I'm wrong - is this behavior working as intended?

[lahmbi5678]

Hi,

you probably should file a bug and CC Eric Pouech, who is doing most of the work on winedbg. Would you have been able to attach to the desired PID, if you entered it in hex format?