Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: law@redhat.com
To: Kevin Buettner <kevinb@redhat.com>
Cc: Fernando Nasser <fnasser@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: so-thresh.exp problems
Date: Thu, 20 Dec 2001 15:28:00 -0000	[thread overview]
Message-ID: <27654.1008890791@porcupine.cygnus.com> (raw)
In-Reply-To: Your message of Thu, 20 Dec 2001 16:06:48 MST. <1011220230648.ZM29801@ocotillo.lan>

  > As one of the solib maintainers, I guess that Jeff's somsolib.c changes
  > are up to me to approve.  I feel kind of funny about this though because
  > I know almost nothing about this file.
It happens ;(  

As its original author, I've got a pretty good idea about what's going on
in somsolib.c -- with the obvious exception of the stuff that came in
from HP (such as the solib-limit stuff).


  > Anyhow, Jeff's somsolib.c change looks okay to me.  Also, as far as
  > I'm concerned, Jeff can check in any other changes that he wants to
  > make to somsolib.c.
Thanks.  I don't forsee needing to do any major surgery; most of the problems
I'm tripping over are related to the insane ttrace code from HP -- which
I doubt anyone outside HP actually understands.

  > (somsolib.c is one of those files that we want
  > bring into the solib-*.c fold.  Anything that's done to it to put it
  > into working order first is more than welcome.)
Feel free to ask questions if you ever want to start trying to bring it
into the fold. 

Conceptually the code isn't terribly different from the other implementations,
but the guts of how we go about getting/setting the information we need is
radically different.  The joys of SOM.

Thanks,
jeff



  reply	other threads:[~2001-12-20 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20 14:28 law
2001-12-20 14:33 ` Fernando Nasser
2001-12-20 15:08   ` Kevin Buettner
2001-12-20 15:28     ` law [this message]
2001-12-20 15:33   ` law
2001-12-21  7:36     ` Fernando Nasser

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=27654.1008890791@porcupine.cygnus.com \
    --to=law@redhat.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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