Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mark Kettenis <kettenis@gnu.org>
To: randolph@tausq.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/RFA/hppa] Make the stub identification code smarter
Date: Thu, 18 Nov 2004 17:01:00 -0000	[thread overview]
Message-ID: <200411181701.iAIH1RPE026059@juw15.nfra.nl> (raw)
In-Reply-To: <20041118012327.GH15714@tausq.org> (message from Randolph Chung on Wed, 17 Nov 2004 17:23:27 -0800)

   Date: Wed, 17 Nov 2004 17:23:27 -0800
   From: Randolph Chung <randolph@tausq.org>

   (Mark: for hppabsd, i don't see any stub handling code. if it uses
   gcc/binutils then i think the same logic for hppa-linux-tdep applies to
   hppabsd-tdep)

AFAIK the BSD's don't use a segmented memory model, and therefore
don't use stubs, but I'm not completely sure about that.

Now that I think of it, OpenBSD/hppa didn't have shared libraries
until very recently.

Mark


  reply	other threads:[~2004-11-18 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18  1:23 Randolph Chung
2004-11-18 17:01 ` mark Kettenis [this message]
2004-11-18 17:11   ` Randolph Chung

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=200411181701.iAIH1RPE026059@juw15.nfra.nl \
    --to=kettenis@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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