Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, Elena Zannoni <ezannoni@redhat.com>,
	David Carlton <carlton@math.stanford.edu>,
	gdb-patches@sources.redhat.com
Subject: Re: [rfa+5.3] bug in my earlier DW_TAG_namespace patch
Date: Mon, 25 Nov 2002 13:37:00 -0000	[thread overview]
Message-ID: <15842.38677.146754.12091@localhost.redhat.com> (raw)
In-Reply-To: <3DE29434.2090205@redhat.com>

Andrew Cagney writes:
 > Hello,
 > 
 > David recommended this for:
 > 
 > #######          #####
 > #               #     #
 > #                     #
 > ######           #####
 >        #   ###         #
 > #     #   ###   #     #
 >   #####    ###    ####
 > 
 > any comments?
 > 

I knew I was forgetting something. 

 > I just noticed that my earlier patch that allowed GDB to accept
 > DW_TAG_namespace entries had a bug in it.  The function
 > scan_partial_symbols in dwarf2read.c only descends into DIEs that have
 > a name; but anonymous namespaces can lead to DIEs without names which
 > have interesting children (where by "interesting" I mean that we want
 > to add partial symbols corresponding to them).  This could result in
 > us missing some partial symbols.
 > 
 > I've enclosed a patch below: for obvious reasons, it should go into
 > GDB 5.3 as well.  I've run GDB on a copy of GDB with this patch
 > applied and followed the control flow when GDB runs into various sorts
 > of DW_TAG_namespace entries, and the control flow seems to behave like
 > I expect it to.  (This is, admittedly, after only a limited amount of
 > testing.)  I'm in the middle of running the testsuite (I'll run it
 > twice, once on a compiler that doesn't generate DW_TAG_namespace
 > entries and once on a compiler that does); assuming that there are no
 > new regressions, is the patch okay?

Were there regressions?

If not, go ahead.

Elena


 > 
 > David Carlton
 > carlton@math.stanford.edu
 > 
 > 2002-11-21  David Carlton  <carlton@math.stanford.edu>
 > 
 > 	* dwarf2read.c (scan_partial_symbols): Descend into namespace
 > 	pdi's with no name.
 > 
 > Index: dwarf2read.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/dwarf2read.c,v
 > retrieving revision 1.75
 > diff -u -p -r1.75 dwarf2read.c
 > --- dwarf2read.c	11 Nov 2002 00:55:34 -0000	1.75
 > +++ dwarf2read.c	22 Nov 2002 00:11:49 -0000
 > @@ -1359,7 +1359,9 @@ scan_partial_symbols (char *info_ptr, st
 >      {
 >        info_ptr = read_partial_die (&pdi, abfd, info_ptr, cu_header);
 >  
 > -      if (pdi.name)
 > +      /* Anonymous namespaces have no name but are interesting.  */
 > +
 > +      if (pdi.name != NULL || pdi.tag == DW_TAG_namespace)
 >  	{
 >  	  switch (pdi.tag)
 >  	    {
 > 


  reply	other threads:[~2002-11-25 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 16:26 David Carlton
2002-11-25 13:20 ` Andrew Cagney
2002-11-25 13:37   ` Elena Zannoni [this message]
2002-11-25 13:43     ` 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=15842.38677.146754.12091@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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