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 16:48:00 -0000	[thread overview]
Message-ID: <20040526164800.GA16564@nevyn.them.org> (raw)
In-Reply-To: <20040526153530.GZ7207@tausq.org>

On Wed, May 26, 2004 at 08:35:30AM -0700, Randolph Chung wrote:
> > 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.
> 
> ok. like this?

Yeah, this is OK.  Thanks.

> 
> randolph
> 
> 2004-05-26  Randolph Chung  <tausq@debian.org>
> 
> 	* Makefile.in (hppa-hpux-tdep.o, hppa-tdep.o): Update dependency.
> 	* hppa-hpux-tdep.c (hppa32_hpux_in_solib_call_trampoline): Use dyncall
> 	and sr4export addresses from tdep structure.
> 	(hppa_hpux_skip_trampoline_code): Likewise.
> 	(hp_cxx_exception_support_initialized): Make static.
> 	(hppa_hpux_observer_inferior_created): New function; reset hp compiler
> 	flags and cached symbols when new inferior is created.
> 	(_initialize_hppa_hpux_tdep): Register for inferior created 
> 	notification.
> 	* hppa-linux-tdep.c (hppa_linux_in_dyncall): Use dyncall address from
> 	tdep structure.
> 	* hppa-tdep.c: Include observer.h
> 	(hppa_observer_inferior_created): New function; listen to inferior
> 	created notification and update addresses in tdep structure.
> 	(_initialize_hppa_tdep): Register for program change notification.
> 	* hppa-tdep.h (struct gdbarch_tdep): Add dyncall, dyncall_external
> 	and sr4export variables.
> 	* symfile.c: (RESET_HP_UX_GLOBALS) Remove HPUXHPPA-specific code.
> 	(symbol_file_add_main_1, symbol_file_clear, reread_symbols): Remove 
> 	HPUXHPPA-specific code.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-05-26 16:48 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
2004-05-26 15:35           ` Randolph Chung
2004-05-26 16:48             ` Daniel Jacobowitz [this message]
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=20040526164800.GA16564@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