From: David Carlton <carlton@math.stanford.edu>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Tolerate filenames present in symtabs but absent from macro info
Date: Wed, 13 Nov 2002 10:49:00 -0000 [thread overview]
Message-ID: <ro1k7jhuwy1.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <vt2adklceek.fsf@zenia.red-bean.com>
On 07 Nov 2002 15:29:07 -0500, Jim Blandy <jimb@redhat.com> said:
> I've committed this.
> Jim Blandy <jimb@redhat.com> writes:
>> 2002-11-01 Jim Blandy <jimb@redhat.com>
>>
>> * macroscope.c: #include "complaints.h".
>> (sal_macro_scope): Cope with filenames that appear in the symtabs,
>> but not in the macro table.
>> * Makefile.in (macroscope.o): Record dependency.
Should PR gdb/621 be closed?
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-11-13 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 9:41 Jim Blandy
2002-11-06 10:24 ` Andrew Cagney
2002-11-06 10:34 ` Andrew Cagney
2002-11-06 12:42 ` Jim Blandy
2002-11-06 12:51 ` Andrew Cagney
2002-11-07 12:44 ` Jim Blandy
2002-11-13 10:49 ` David Carlton [this message]
2002-11-13 11:26 ` 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=ro1k7jhuwy1.fsf@jackfruit.Stanford.EDU \
--to=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