From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 844 invoked by alias); 18 Mar 2005 03:40:39 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 792 invoked by uid 48); 18 Mar 2005 03:40:36 -0000 Date: Fri, 18 Mar 2005 03:40:00 -0000 Message-ID: <20050318034036.791.qmail@sourceware.org> From: "paul at codesourcery dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20050317143206.794.paul@codesourcery.com> References: <20050317143206.794.paul@codesourcery.com> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/794] Segfault with LD_DEBUG=ALL X-Bugzilla-Reason: CC X-SW-Source: 2005-03/txt/msg00089.txt.bz2 List-Id: ------- Additional Comments From paul at codesourcery dot com 2005-03-18 03:40 ------- This happened with an internal modified version of glibc, and only occurred because another bit of glibc was broken. However tracking down that bug would probably have been easier if _dl_debug_printf didn't segfault. Tracking back a fault is much easier when you can see the debug output going wrong, rather than trying to deal with segfaults on a target without a working gdb. The issue is not specific to a particular target. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW 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.