From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-1898-listarch-glibc-bugs=sources.redhat.com@sources.redhat.com>
Received: (qmail 7996 invoked by alias); 17 Mar 2005 14:32:22 -0000
Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:glibc-bugs-subscribe@sources.redhat.com>
List-Post: <mailto:glibc-bugs@sources.redhat.com>
List-Help: <mailto:glibc-bugs-help@sources.redhat.com>, <http://sources.redhat.com/lists.html#faqs>
Sender: glibc-bugs-owner@sources.redhat.com
Received: (qmail 7666 invoked by uid 48); 17 Mar 2005 14:32:12 -0000
Date: Thu, 17 Mar 2005 14:32:00 -0000
From: "paul at codesourcery dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Message-ID: <20050317143206.794.paul@codesourcery.com>
Reply-To: sourceware-bugzilla@sources.redhat.com
Subject: [Bug libc/794] New: Segfault with LD_DEBUG=ALL
X-Bugzilla-Reason: CC
X-SW-Source: 2005-03/txt/msg00081.txt.bz2
List-Id: <glibc-bugs.sourceware.org>

I'm getting a segfault when setting LD_DEBUG=all
The segfault occurs because we end up doing something equivalent to 
_dl_debug_printf("%s", NULL);

I't quite possible that this is a bug elsewhere, but given this routine is
specifically for debugging purposes it sems sensible to make it robust to
unusual input.

-- 
           Summary: Segfault with LD_DEBUG=ALL
           Product: glibc
           Version: 2.3.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: paul at codesourcery dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-none-linux-gnueabi


http://sources.redhat.com/bugzilla/show_bug.cgi?id=794

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.