From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12730 invoked by alias); 24 Apr 2002 05:03:14 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12719 invoked from network); 24 Apr 2002 05:03:13 -0000 Received: from unknown (HELO pizda.ninka.net) (216.101.162.242) by sources.redhat.com with SMTP; 24 Apr 2002 05:03:13 -0000 Received: from localhost (IDENT:davem@localhost.localdomain [127.0.0.1]) by pizda.ninka.net (8.9.3/8.9.3) with ESMTP id VAA25887; Tue, 23 Apr 2002 21:53:51 -0700 Date: Tue, 23 Apr 2002 22:03:00 -0000 Message-Id: <20020423.215351.41174202.davem@redhat.com> To: msnyder@redhat.com Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] Time for a shared linux-nat.c module? From: "David S. Miller" In-Reply-To: <3CC5C242.D975892F@redhat.com> References: <3CC5C242.D975892F@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00911.txt.bz2 From: Michael Snyder Date: Tue, 23 Apr 2002 13:21:22 -0700 I notice that there are now a bunch of -linux-tdep.c modules, and that some of them share a bunch of duplicate code. I'm wondering if it isn't time to create a linux-nat.c module, shared by all host architectures, into which we can move some of this code instead of maintaining separate, duplicate versions. The code won't be even Linux specific, I think. For example the dynamic linker checks are glibc specific. The commentary refers to it as the "Hurd" resolver, but in fact it is more of a glibc thing than anything else. ${cpu}_linux_skip_solib_resolver is what I'm specifically talking about and we can put that as glibc_skip_solib_resolver in glibc-tdep.c or something like that. The rest doesn't look all that sharable, as they deal with signal frame specifics which are quite CPU dependent.