public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egreen at datadomain dot com" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/365] New: During out of memory condition syslog.c generates message with unprintable characters Date: Fri, 03 Sep 2004 00:08:00 -0000 [thread overview] Message-ID: <20040903000840.365.egreen@datadomain.com> (raw) [-- 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.
next reply other threads:[~2004-09-03 0:08 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-03 0:08 egreen at datadomain dot com [this message] 2004-09-12 18:19 ` [Bug libc/365] " drepper at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040903000840.365.egreen@datadomain.com \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).