Handle failure to open /proc/pid/comm file

We only try to open comm files in directories under /proc that start
with a digit. Now, I don't think I've ever seen a /proc directory entry
that began with a digit (or was all digits) and wasn't a process
directory, but lets handle this scenario just in case.

Signed-off-by: Andrew Clayton <andrew@digital-domain.net>