From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5554 invoked by alias); 11 Feb 2004 00:04:58 -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 5540 invoked from network); 11 Feb 2004 00:04:57 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 11 Feb 2004 00:04:57 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1Aqhs9-0002Wd-6U; Tue, 10 Feb 2004 19:04:57 -0500 Date: Wed, 11 Feb 2004 00:04:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa/mips] Shared library trampoline support for mips-linux Message-ID: <20040211000457.GA9655@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb-patches@sources.redhat.com References: <20040210231538.GA8420@nevyn.them.org> <40296B8A.5060502@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40296B8A.5060502@gnu.org> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-02/txt/msg00269.txt.bz2 On Tue, Feb 10, 2004 at 06:38:50PM -0500, Andrew Cagney wrote: > >- /* Hook in OS ABI-specific overrides, if they have been registered. */ > >- gdbarch_init_osabi (info, gdbarch); > >- > > set_gdbarch_skip_trampoline_code (gdbarch, mips_skip_stub); > > > > set_gdbarch_in_solib_call_trampoline (gdbarch, mips_in_call_stub); > > set_gdbarch_in_solib_return_trampoline (gdbarch, mips_in_return_stub); > > Assuming that the default is no OS, I'm actually wondering why these are > set at all. Because they're used for MIPS16, presumably. The fact that MIPS16 call stubs use the solib machinery is why I had a ??? in my question. > >+ /* Hook in OS ABI-specific overrides, if they have been registered. */ > >+ gdbarch_init_osabi (info, gdbarch); > > >+#undef IN_SOLIB_DYNSYM_RESOLVE_CODE > >+#define IN_SOLIB_DYNSYM_RESOLVE_CODE(PC) > >mips_linux_in_dynsym_resolve_code (PC) > > ulgh, still not multi-arched :-( Yeah. I spent a little while thinking about how to multi-arch it and couldn't come up with a good solution, so I let it be. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer