public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul at codesourcery dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/794] New: Segfault with LD_DEBUG=ALL
Date: Thu, 17 Mar 2005 14:32:00 -0000	[thread overview]
Message-ID: <20050317143206.794.paul@codesourcery.com> (raw)

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.


             reply	other threads:[~2005-03-17 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 14:32 paul at codesourcery dot com [this message]
2005-03-17 14:35 ` [Bug libc/794] " paul at codesourcery dot com
2005-03-17 21:09 ` roland at gnu dot org
2005-03-18  3:40 ` paul at codesourcery dot com
2005-03-20  2:06 ` gotom at debian dot or dot jp
2005-03-20  6:39 ` roland at gnu dot org

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=20050317143206.794.paul@codesourcery.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: link
Be 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).