Geoff Chappell - Software Analyst
This option restricts DUMPBIN’s attention to a particular range of image-file addresses.
One or two arguments are required. It is a fatal error (LNK1117) to provide more than two arguments. If an argument has the form property=value, the property is ignored without complaint. Each argument must be numerical, in decimal, hexadecimal or octal notation, with no sign prefix, evaluated as an unsigned integer truncated to 64 bits. Anything else is a fatal error (LNK1147).
This option applies only to executables in PE format.
The first and last arguments are addresses as if the image is loaded at its expected base address (as given in the Optional Header). The range is inclusive: from first up to and including last.
Each /range overrides the first from any earlier /range. Each /range that sets a last overrides the last from any earlier /range. No check is ever made that first is less than last: the consequences of not satisfying this common-sense requirement are here regarded as undefined.
Many DUMPBIN options enable the dumping of some corresponding file feature as part of the dumping of whatever section contains the data for this feature. To be eligible for such dumps, a section in an applicable input file must be eligible with respect to /section and with respect to /range. To be eligible with respect to /range means that either the section must have at least some intersection with the specified range or there is no /range option.
For each applicable input file, for each section that is eligible with respect to /section, if the section has no intersection with the specified range, DUMPBIN ignores the section without complaint. The dumps enabled by the /disasm and /rawdata options are further restricted. Within the eligible sections, the dumps of code and data are restricted just to the addresses in the specified range.
This option is not documented in the January 2004 edition of the MSDN Library on CD.