On Sun, Aug 31, 2008 at 08:40:06PM -0700, Daniel Burrows <[EMAIL PROTECTED]> was heard to say: > It looks to me like something is copying into a fixed-length buffer > and truncating the string. It's not running off the end (or valgrind > would have squawked about that and the strings would probably have > sometimes been correct), but since the string isn't NUL-terminated, we > end up printing a bunch of garbage (whatever's at the end of the > string).
cwidget's swsprintf doesn't handle overflows of its initial buffer correctly at all -- there are at least two bugs in it (one of which doesn't crash the program only because the other bug means it never runs). Now that I've tracked it down, it should be pretty easy to fix. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
