Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] generate symbols associated to namespaces
Date: Tue, 09 Sep 2003 22:17:00 -0000	[thread overview]
Message-ID: <16222.18907.572350.938649@localhost.redhat.com> (raw)
In-Reply-To: <yf2he3lu2os.fsf@hawaii.kealia.com>

David Carlton writes:
 > On Tue, 9 Sep 2003 15:51:37 -0400, Elena Zannoni <ezannoni@redhat.com> said:
 > > David Carlton writes:
 > 
 > >> +	  psym = add_psymbol_to_list (pdi->name, strlen (pdi->name),
 > >> +				      VAR_DOMAIN, LOC_STATIC,
 > >> +				      &objfile->static_psymbols,
 > >> +				      0, addr + baseaddr,
 > >> +				      cu_language, objfile);
 > 
 > > I don't like this too much. I.e. changing add_psymbol_to_list to
 > > return a value so you can get a hold of the psym. After all,
 > > add_psymbol_to_list doesn't change any of the fields of the psymbol,
 > > and cp_check_possible_namespace_symbols uses 2 fields that you
 > > already have around.
 > 
 > No, add_psymbol_to_list does change the fields: it calls
 > SYMBOL_SET_NAMES to set the demangled name, which I need in
 > cp_check_possible_namespace_symbols.  So having add_psymbol_to_list
 > return the psymbol seems the best solution; I suppose I could break
 > out the demangled-name-caching code that SYMBOL_SET_NAMES uses into a
 > separate function, but it doesn't seem worth it here.
 > 

Oh, right.  I really don't like it.  Only these few callers of
add_psymbol_to_list use its return value.  But you are right, that
function does quite a bit. Sigh. I don't see any alternative, then.

Ok on the rest.

elena



  reply	other threads:[~2003-09-09 22:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 20:22 David Carlton
2003-06-22 17:42 ` Daniel Jacobowitz
2003-06-24 19:00   ` David Carlton
2003-06-24 19:02     ` Daniel Jacobowitz
2003-06-27 16:04       ` David Carlton
2003-06-27 21:58         ` David Carlton
2003-06-27 22:32           ` David Carlton
2003-08-05 16:30           ` David Carlton
2003-08-05 17:54           ` Daniel Jacobowitz
2003-08-05 18:06             ` David Carlton
2003-08-05 18:08               ` Daniel Jacobowitz
2003-08-05 18:18                 ` David Carlton
2003-08-31 19:29             ` Daniel Jacobowitz
2003-09-02 16:38               ` David Carlton
2003-09-09 19:42           ` Elena Zannoni
2003-09-09 20:28             ` David Carlton
2003-09-09 22:17               ` Elena Zannoni [this message]
2003-09-09 23:25                 ` David Carlton
2003-09-11 19:52                   ` David Carlton
2003-09-17 20:41                     ` David Carlton
2003-09-11 23:28             ` [rfa] use allocate_block more David Carlton
2003-09-11 23:33               ` Elena Zannoni
2003-09-11 23:44                 ` David Carlton

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=16222.18907.572350.938649@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@kealia.com \
    --cc=gdb-patches@sources.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