[Guy Harris <guy@xxxxxxxxxx>]

> It was actually already there, just didn't use the %o format - was lumped in
> with %d/%u for the int/uint. I made the change for the four places it did
> the format. It's not clear at this point if %o will work properly with a int
> as opposed to an unsigned int though.

Define "properly".  The ANSI C spec for "fprintf()" says

	o,u,x,X    The "unsigned int" argument is converted to unsigned
		   octal (o), unsigned decimal (u), or unsigned
		   hexadecimal notation (x or X) in the style "dddd";
		   ...

I.e., just as "%x" and "%X" will always print the number as if it were
unsigned, "%o" will always print the number as if it were signed.

If this is a problem, it's presumably not only a problem for octal, it's
presumably also a problem for hex.