Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Nicholas Duffek <nsd@redhat.com>, gdb-patches@sources.redhat.com
Cc: jimb@cygnus.com, kevinb@cygnus.com
Subject: Re: [RFA] osfsolib.c: support Tru64 5.x
Date: Sun, 13 May 2001 00:06:00 -0000	[thread overview]
Message-ID: <1010513070637.ZM31193@ocotillo.lan> (raw)
In-Reply-To: <200105122347.TAA16895@nog.bosbc.com>

On May 12,  7:47pm, Nicholas Duffek wrote:

> 	* osfsolib.c: Update libxproc.a comment.
> 	(ldr_module_info_t): Declare some unknown fields as char *
> 	instead of CORE_ADDR.
> 	(ldr_context_t): Document.
> 	(solib_cleanup_queued): New variable.
> 	(do_clear_solib, link_map_member): New functions.
> 	(first_link_map_member, next_link_map_member): Split large "if"
> 	conditional into multiple conditionals.  Rename {first,next}_lm
> 	to lm.  Move common code to link_map_member().
> 	(find_solib): Call make_run_cleanup().
> 	(clear_solib): Delete free_all_symtabs comment.  Don't call
> 	disable_breakpoints_in_shlibs().

Nick,

Is there any chance that osfsolib.c could be reworked into a solib.c
backend?  (See solib-svr4.c and solib-aix5.c for examples.)  I don't
know if you have the time and/or energy to work on this at the moment,
but that's what I would like to see done.  (Eventually, anyway.)

In the interim, I think your patch can go in so long as you've tested it
on Tru64 4.x and 5.x.

Kevin


  reply	other threads:[~2001-05-13  0:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-12 16:45 Nicholas Duffek
2001-05-13  0:06 ` Kevin Buettner [this message]
2001-05-14 18:34   ` Nick Duffek
2001-05-15 17:02     ` Kevin Buettner
2001-05-24 18:58       ` Nick Duffek
     [not found] <1010525224132.ZM16493@ocotillo.lan>
2001-05-25 17:37 ` Nick Duffek
2001-05-25 18:08   ` Kevin Buettner
2001-05-25 17:55 ` Nick Duffek

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=1010513070637.ZM31193@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@cygnus.com \
    --cc=nsd@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