Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/mips] Shared library trampoline support for mips-linux
Date: Wed, 11 Feb 2004 18:33:00 -0000	[thread overview]
Message-ID: <402A757D.9020904@gnu.org> (raw)
In-Reply-To: <20040211000457.GA9655@nevyn.them.org>

> 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.

If you can wrap those two in an "if (osabi isn't for an os)", and add a 
rude comment, I'm ok.

I get the feeling that infrun should just have a list of per-osabi 
function names that it either silently step-outof or finishes.  If it 
were user visible, people could even add to it.

Andrew



  reply	other threads:[~2004-02-11 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 23:15 Daniel Jacobowitz
2004-02-10 23:38 ` Andrew Cagney
2004-02-11  0:04   ` Daniel Jacobowitz
2004-02-11 18:33     ` Andrew Cagney [this message]
2004-02-11 18:48       ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=402A757D.9020904@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox