@labath another instance of this 32/64 length parsing/error dance and subsequent "isValid" checking following it that'd be great to tidy up with a common utility for parsing the length and returning a length-constrained DWARFDataExtractor for further use.
Thanks! I'll change the name, as well as for the other similar instances.
Could you explain why unsinged is better than int here?
Note that according to http://www.cplusplus.com/reference/cstdio/printf/,
Not "an unsigned integer value".
IIRC, the DataExtractor class provides an optional second argument to its get... methods that can be used to specify an Error to pass any problems back in, including reading past the end. Would it make some sense to use that instead of the isValid... checks?
I find the following link tends to be more precise and accurate in its wording:
I don't have a copy of the standard to see whether the type is explicitly mentioned, but that quote definitively says int.