Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess
Date: Wed, 19 May 2004 22:06:00 -0000	[thread overview]
Message-ID: <20040519220655.GM10684@gnat.com> (raw)
In-Reply-To: <20040519214440.GV566@tausq.org>

> > I was going to add the event at the begining of exec.c:exec_file_attach().
> > Would that work for you as well?
> 
> exec_file_attach () seems to be called before the symbols are read into
> gdb. If so the lookups that I need to do will not work. Am I right?

Yes you are right. I didn't look at your patch closely enough to
see that you were going to do symbol lookups during the notification.

> I can change the hppa code to do lazy init if we use this approach;
> just need to understand the semantics :)

I don't want to force you to take any approach. A signal at symbol
file update is good too. However, could you in that case use a different
name for the observer, I found it confusing since the notification is not
necessarily emitted when the program has been changed. Something like
program_symbols_changed?

We'll have two observers instead of one: One for the executable changed,
and one for the program symbols changed.

I don't know what the other maintainers will think about this?

-- 
Joel


  reply	other threads:[~2004-05-19 22:06 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 [this message]
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               ` [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=20040519220655.GM10684@gnat.com \
    --to=brobecker@gnat.com \
    --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