The file contains:
logger.log(Level.FINE, "Libunwind: findProcInfo for 0x"
+ Long.toHexString(instructionAddress) + "\n");
(it also contained references to frysk.proc.Host.logger, but that is another
story :-), in particular, note the use of the << + >> operator. That causes the
allocation of a StringBuffer even when there's no log message.
The code should instead use the logger's formatting mechanism.
(It's suspected that the code was simply translated from System.out.println calls).
January 11, 2007
* StackCallbacks.java (accessReg): Use logger formatting mechanism, bug #3216
(accessMem): Ditto. Cleaned up some excessive logging junk.