From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18294 invoked by alias); 7 Aug 2008 19:58:38 -0000 Received: (qmail 18282 invoked by uid 22791); 7 Aug 2008 19:58:37 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 07 Aug 2008 19:58:01 +0000 Received: (qmail 25403 invoked from network); 7 Aug 2008 19:58:00 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 7 Aug 2008 19:58:00 -0000 Message-ID: <489B53BA.3040607@codesourcery.com> Date: Thu, 07 Aug 2008 19:58:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Doug Evans CC: gdb@sourceware.org Subject: Re: sol-thread.c core_ops oddity References: <20080807191136.274F81C77BE@localhost> <20080807192518.GA31697@caradoc.them.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00142.txt.bz2 Doug Evans wrote: > On Thu, Aug 7, 2008 at 12:25 PM, Daniel Jacobowitz wrote: > >> On Thu, Aug 07, 2008 at 12:11:36PM -0700, Doug Evans wrote: >> >>> Obviously I'm missing something. >>> I don't have a solaris system to see what really happens, >>> can someone fill in the missing piece that makes the above work? >>> >> Luck and sorting. I'm pretty sure we generate the calls in >> alphabetical order (by filename or by function, I'm not sure). >> > > Thanks. I don't see any sorting beyond > INIT_FILES = $(COMMON_OBS) $(TSOBS) $(CONFIG_SRCS) > and the hack for gdbtypes. > Is there an intention to officially sanction the sorting as something > one can take advantage of? > *I'm* not going to officially sanction any particular sort order, we have enough tricky implicit bits already. Maybe we should have the daily checkin change the initialization order randomly, so as to catch misbehaving code... 1/2 :-) Stan