[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[drepper @ gnu . org: Re: libc/5025]

From: Igor Homyakov
Subject: [drepper @ gnu . org: Re: libc/5025]
Date: Wed, 21 May 2003 11:34:02 +0400
User-agent: Mutt/1.4.1i

----- Forwarded message from drepper @ gnu . org -----

Date: Wed, 21 May 2003 03:22:23 -0400
From: address@hidden
To: libc-gnats @ gnu . org, igor.homyakov @ ramax . ru, drepper @ gnu . org
Subject: Re: libc/5025

Synopsis: syslog crashes with heap corruption in malloc

State-Changed-From-To: open->suspended
State-Changed-By: drepper
State-Changed-When: Wed, 21 May 2003 03:22:23 -0400
Every program which crashes is glibc's fault.  Get real. 
Any malloc operation after a heap corruption will cause the
program to crash at the next allocation.  A bug in the
program before a syslog() call will cause syslog to fail but
it is not the cause.

Debug your program, find out where the program is.  There
are millions of programs using syslog and therefore is
chance that the bug is in your code is indefinitely higher.

Until we get concrete evidence that syslog is at fault the
bug is suspended.

----- End forwarded message -----
Igor Homyakov
<homyakov at altlinux dot ru>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]