public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/365] New: During out of memory condition syslog.c generates message with unprintable characters
@ 2004-09-03 0:08 egreen at datadomain dot com
2004-09-12 18:19 ` [Bug libc/365] " drepper at redhat dot com
0 siblings, 1 reply; 2+ messages in thread
From: egreen at datadomain dot com @ 2004-09-03 0:08 UTC (permalink / raw)
To: glibc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
During an out of memory condition syslog.c generated and "out of memory" message
to syslog. This message was supposed to contain the pid, but not only contained
the pid but garbage characters as well. The message it generated is the following:
Aug 20 05:25:07 mdd200 out of memory [617ÿÿÿÿout o]
The bug appears to be at line 158 of the 2.2.5 version of syslog.c which is the
following:
endp = __mempcpy (endp, nump, (nump + sizeof (numbuf)) - nump);
The same source code appears at line 159 of the 2.3.2 version of syslog c which
is the following:
endp = __mempcpy (endp, nump, (nump + sizeof (numbuf)) - nump);
The fix should be the following:
endp = __mempcpy (endp, nump, (numbuf + sizeof (numbuf)) - nump);
The offset into numbuf is not being properly calculated and therefore the wrong
number of bytes are being copied which accounts for the unprintable (garbage
characters).
The company I work for creates software that needs to generate email
notifications when failures occur in our product. The failure we were trying to
report was the out of memory condition. Part of our emails include the syslog
messages file. Due to this bug the email got truncated at the first unprintable
character and we lost the critical, informative data that we include after the
message file content.
Quick attention to fixing this bug ASAP is greatly appreciated.
--
Summary: During out of memory condition syslog.c generates
message with unprintable characters
Product: glibc
Version: 2.2.5
Status: NEW
Severity: critical
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: egreen at datadomain dot com
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=365
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug libc/365] During out of memory condition syslog.c generates message with unprintable characters
2004-09-03 0:08 [Bug libc/365] New: During out of memory condition syslog.c generates message with unprintable characters egreen at datadomain dot com
@ 2004-09-12 18:19 ` drepper at redhat dot com
0 siblings, 0 replies; 2+ messages in thread
From: drepper at redhat dot com @ 2004-09-12 18:19 UTC (permalink / raw)
To: glibc-bugs
------- Additional Comments From drepper at redhat dot com 2004-09-12 18:19 -------
Fixed in CVS.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://sources.redhat.com/bugzilla/show_bug.cgi?id=365
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-09-12 18:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-03 0:08 [Bug libc/365] New: During out of memory condition syslog.c generates message with unprintable characters egreen at datadomain dot com
2004-09-12 18:19 ` [Bug libc/365] " drepper at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).