I can no longer reproduce this on Solaris x86 with rev 71123, so I'm assuming
it has been fixed.  Closing report.