Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: jtc@redback.com (J.T. Conklin)
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] Add solib-aix5.c for AIX5 shared library support
Date: Tue, 20 Feb 2001 13:48:00 -0000	[thread overview]
Message-ID: <5mr90t6n73.fsf@jtc.redback.com> (raw)
In-Reply-To: <1010220211458.ZM26261@ocotillo.lan>

>>>>> "Kevin" == Kevin Buettner <kevinb@cygnus.com> writes:
Kevin> I am starting to merge the native port of GDB for AIX5/IA-64.  The
Kevin> patch below adds a new file solib-aix5.c to the gdb sources.  I have
Kevin> not tested this code yet on the traditional AIX architectures (Power,
Kevin> PPC), but it is my hope that it will be usable by those architectures
Kevin> as well.

I'm not qualified to comment on the meat of the patch, but it seems
like there are some svr4 bits that could be removed.  

For example, AIX 5 probably doesn't have the plethora of symbol names
found in all the svr4 varients (c.f. solib_break_names, bkpt_names). 
Also, in_svr4_dynsym_resolve_code() collides with a function of the
same name in solib-svr4.c (not that they'll be linked in the same GDB
now, but we shouldn't prelude the ability to do so in the future).
There is also a comment about FreeBSD stripping the dynamic linker,
which certainly sounds like it wouldn't be an issue on AIX.

For a new file, I'd also get rid of all the STREQ() calls and replace
them with the corresponding strcmp().

        --jtc

-- 
J.T. Conklin
RedBack Networks


  reply	other threads:[~2001-02-20 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 13:15 Kevin Buettner
2001-02-20 13:48 ` J.T. Conklin [this message]
2001-02-20 14:01   ` Kevin Buettner

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=5mr90t6n73.fsf@jtc.redback.com \
    --to=jtc@redback.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=kevinb@cygnus.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