Package: msr-tools
Version: 1.3-2
Severity: wishlist
Tags: upstream
Dear Maintainer,
I tried to use rdmsr to read a particular MSR using:
# rdmsr MSR_K8_TOP_MEM2
Thinking that if it didn't know what MSR_K8_TOP_MEM2 was it would produce an
error and I could look up the proper number. Instead it said "0" which was a
plausible answer and so I carried on.
However it turns out that it actually read whatever MSR
strtoul("MSR_K8_TOP_MEM2", NULL, 0) produces, which is unlikely to be the MSR
which was wanted.
It would be great if there could be some sanity checking of the input and/or
the error checks on the strtoul.
The strtoul(3) manpage suggests setting errno=0 before calling strtoul and then
checking for no-zero errno afterwards, since 0 is a legitimate converstion
result.
`
Thanks,
Ian.
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages msr-tools depends on:
ii libc6 2.19-18
msr-tools recommends no packages.
msr-tools suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
