From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7888 invoked by alias); 19 Nov 2009 00:31:09 -0000 Received: (qmail 7844 invoked by uid 48); 19 Nov 2009 00:30:55 -0000 Date: Thu, 19 Nov 2009 00:31:00 -0000 Message-ID: <20091119003055.7843.qmail@sourceware.org> From: "roland at gnu dot org" To: glibc-bugs@sources.redhat.com In-Reply-To: <20060211192240.2328.jreiser@BitWagon.com> References: <20060211192240.2328.jreiser@BitWagon.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/2328] _dl_debug_state() RT_CONSISTENT called too early X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00110.txt.bz2 ------- Additional Comments From roland at gnu dot org 2009-11-19 00:30 ------- I'm not at all sure this change would be right. Someone might want to test where the RT_CONSISTENT breakpoint happens in relation to relocation on Solaris. AFAICT the RT_CONSISTENT state is purely about the state of the r_debug.r_map list and all those pointers. It says you can get the list of objects mapped in core now, that is all. It might be OK to move RT_CONSISTENT to after relocation, but we should be cautious about that. It's been as it is for a very long time. How best to make GDB and libthread_db startup work right is really another question. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2328 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.