On Wed, Dec 21, 2005 at 10:22:56AM -0600, Duane Meyer wrote: > Package: openssh-server > Version: 1:4.2p1-5 > Severity: grave > Justification: renders package unusable > This all seems to have started since the last update I ran on or around the > 19th of December 2005 which included a new 2.4.27 Kernel. > Some time ago, I needed to set an environment variable to fix what seemed to be a related problem. Nobody was able to connect via SSH to the server. > The fix seemed to relate to a double free of a memory chunk which caused > an updated glibc to abort the running program. So setting MALLOC_CHECK_=0 > would magically force glibc to ignore the error and keep running. Maybe it's > not related at all but the behavior looks suspiciously famliar. Ok, so by setting MALLOC_CHECK_=0, you've hidden a bug in some part of the software, possibly leading to a segfault later; a bug that no one else is seeing and that you'll have to get us a backtrace of in order for anyone to debug. Please see http://wiki.debian.org/HowToGetABacktrace for some information on how to get a backtrace for a crashing program. You will want to run this first *without* MALLOC_CHECK_=0, so we can fix that first and look at the segfault afterwards only if you continue to experience it. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature