From: Jim Blandy <jimb@redhat.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] C++ Dwarf2 inner scope PR/789
Date: Mon, 04 Nov 2002 13:19:00 -0000 [thread overview]
Message-ID: <vt2smyhhwr7.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <200210282137.QAA31170@makai.watson.ibm.com>
David Edelsohn <dje@watson.ibm.com> writes:
> Any status on PR gdb/789 and the patch earlier in this thread?
I think the patch breaks into two parts:
First, restoring local_symbols and param_symbols from the popped
context seems right. That's a two-line fix, so I'll just make it
myself, with credit to you.
I think restoring prev_list_in_scope can be done more simply, by
checking whether context_stack is empty: if it is, then the list in
scope is file_symbols; otherwise, it's local_symbols.
However, I've seen some odd behavior when running your test case that
I want to understand before I proceed with this. I appreciate your
patience.
next prev parent reply other threads:[~2002-11-04 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 21:10 David Edelsohn
2002-10-10 13:26 ` Jim Blandy
2002-10-10 13:27 ` David Edelsohn
2002-10-28 13:37 ` David Edelsohn
2002-11-04 13:19 ` Jim Blandy [this message]
2002-10-10 13:27 ` Jim Blandy
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=vt2smyhhwr7.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=dje@watson.ibm.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