Displaying 2 results from an estimated 2 matches for "next_msg".
Did you mean:
net_msg
2000 Nov 01
0
FreeBSD Security Advisory: FreeBSD-SA-00:62.top
...top/display.c,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- display.c 1999/01/09 20:20:33 1.4
+++ display.c 2000/10/04 23:34:16 1.5
@@ -829,7 +831,7 @@
register int i;
/* first, format the message */
- (void) sprintf(next_msg, msgfmt, a1, a2, a3);
+ (void) snprintf(next_msg, sizeof(next_msg), msgfmt, a1, a2, a3);
if (msglen > 0)
{
Index: top.c
===================================================================
RCS file: /mnt/ncvs/src/contrib/top/top.c,v
retrieving revisi...
2016 Mar 31
0
[Bug 1060] New: Garbage output
...a while, it's a complete log clutter and waste of resources.
The problem is present in the latest git version, but seems to have been there
for a while:
$ grep -n 'printf.*\(first\|next\)' src/*
src/libipulog_compat.c:136: printf("first\n");
src/libipulog_compat.c:139:next_msg: printf("next\n");
Those printfs seem to have been forgotten when debugging, I'd say.
Sure it's possible to workaround (redirecting the output somewhere in the
middle?) but the methods aren't exactly desirable so I'd recommend fixing this.
Best regards.
--
You are...