From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Randolph Chung <randolph@tausq.org>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess
Date: Fri, 28 May 2004 23:43:00 -0000 [thread overview]
Message-ID: <20040528234344.GA11062@nevyn.them.org> (raw)
In-Reply-To: <40B4D9D6.7040302@gnu.org>
On Wed, May 26, 2004 at 01:54:30PM -0400, Andrew Cagney wrote:
> >+static void
> >+hppa_hpux_observer_inferior_created (struct target_ops *objfile, int
> >from_tty)
> >+{
> >+ struct gdbarch_tdep *tdep;
> >+ struct minimal_symbol *minsym;
> >+
> >+ tdep = gdbarch_tdep (current_gdbarch);
> >+
> >+ /* Some HP-UX related globals to clear when a new "main"
> >+ symbol file is loaded. HP-specific. */
> >+
> >+ /* Indicates HP-compiled code. */
> >+ deprecated_hp_som_som_object_present = 0;
> >+ /* Must reinitialize exception stuff. */
> >+ hp_cxx_exception_support_initialized = 0;
> >+
> >+ 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;
> >+}
>
> Unfortunatly, not really but as you've noticed, it does ``work'', sigh.
> At least we can now see what the code is doing.
>
> The above values are dependant on the inferior (and make change between
> inferior invocations) and not the architecture so their lifetime should
> be bound to the inferior. This patch binds them to the current
> ``global'' architecture :-(
... but forces them to update every time the inferior restarts. Yes,
if we have multiple inferiors sharing an architecture this won't work.
I think that's true of many mutable fields in various targets' tdep.
They need to migrate to a per-inferior data object someday.
> Can, for the immediate term, hppa_hpux_skip_trampoline_code be
> simplified so that it doesn't even try to cache these values? This will
> put a real strain on the symtab but I think its the symtab that is the
> place that needs the fix.
What's wrong with the symtab here?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-28 23:43 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
2004-05-26 17:54 ` [patch/rfc] New program_changed event, cleanup some HPUXHPPAmess Andrew Cagney
2004-05-28 23:43 ` Daniel Jacobowitz [this message]
2004-05-31 19:43 ` 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=20040528234344.GA11062@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