Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess
Date: Wed, 26 May 2004 13:25:00 -0000	[thread overview]
Message-ID: <20040526132546.GB7594@nevyn.them.org> (raw)
In-Reply-To: <20040526052753.GU7207@tausq.org>

On Tue, May 25, 2004 at 10:27:53PM -0700, Randolph Chung wrote:
> > >assuming the attach case also works, this should be ok for what i need.
> > 
> > That code was added for a similar problem so it looks hopeful.
> 
> seems to be ok. here's the new version, using the inferior_created 
> event you checked in. still passes all the tests that used to pass 
> before :)
> 
> ok to checkin?

Almost, just one thing I'd like you to fix.

> +static void
> +hppa_observer_inferior_created (struct target_ops *objfile, int from_tty)
> +{
> +  struct gdbarch_tdep *tdep;
> +  struct minimal_symbol *minsym;
> +
> +  tdep = gdbarch_tdep (current_gdbarch);
> +
> +  minsym = lookup_minimal_symbol ("$$dyncall", NULL, NULL);
> +  if (minsym)
> +    tdep->dyncall = SYMBOL_VALUE_ADDRESS (minsym);
> +  else
> +    tdep->dyncall = -1;
> +
> +  /* These are HPUX only.  */

If this comment is right, why not move these to the hppa-hpux specific
observer?  If the comment is wrong, just remove it, but it looks right.

> +  minsym = lookup_minimal_symbol ("$$dyncall_external", NULL, NULL);
> +  if (minsym)
> +    tdep->dyncall_external = SYMBOL_VALUE_ADDRESS (minsym);
> +  else
> +    tdep->dyncall_external = -1;
> +
> +  minsym = lookup_minimal_symbol ("_sr4export", NULL, NULL);
> +  if (minsym)
> +    tdep->sr4export = SYMBOL_VALUE_ADDRESS (minsym);
> +  else
> +    tdep->sr4export = -1;
> +}


-- 
Daniel Jacobowitz


  reply	other threads:[~2004-05-26 13:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 20:40 Randolph Chung
2004-05-19 21:37 ` Joel Brobecker
2004-05-19 21:44   ` Randolph Chung
2004-05-19 22:06     ` Joel Brobecker
2004-05-21 18:48 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-21 19:02   ` [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Randolph Chung
     [not found]     ` <40AE6260.2090205@gnu.org>
2004-05-26  5:27       ` Randolph Chung
2004-05-26 13:25         ` Daniel Jacobowitz [this message]
2004-05-26 15:35           ` Randolph Chung
2004-05-26 16:48             ` Daniel Jacobowitz
2004-05-26 17:54             ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-28 23:43               ` [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Daniel Jacobowitz
2004-05-31 19:43                 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-31 20:43                   ` [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess Daniel Jacobowitz
2004-06-01  1:31                     ` Andrew Cagney
2004-06-01  1:40                       ` Daniel Jacobowitz
2004-06-03 17:41                       ` Randolph Chung
2004-06-04 18:26                         ` Andrew Cagney
2004-05-24 15:45   ` Randolph Chung
2004-05-24 18:55     ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney

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=20040526132546.GB7594@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@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