From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: make `info source' say whether macro info is present
Date: Thu, 23 May 2002 05:36:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020523075506.25853C-100000@is> (raw)
In-Reply-To: <20020522201700.952B45EA11@zwingli.cygnus.com>
On Wed, 22 May 2002, Jim Blandy wrote:
> This will make it a bit easier to write tests that exit gracefully
> when the test executable doesn't have any information about
> preprocessor macros. Alternative suggestions welcome.
>
> gdb/ChangeLog:
> 2002-05-22 Jim Blandy <jimb@redhat.com>
>
> * source.c (source_info): Mention whether the symtab has
> information about preprocessor macros.
Jim, I think gdb.texinfo should be updated to match this change, where
"info source" is documented.
next prev parent reply other threads:[~2002-05-23 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 14:28 Jim Blandy
2002-05-23 5:36 ` Eli Zaretskii [this message]
2002-05-23 13:57 ` Jim Blandy
2002-05-24 5:20 ` Eli Zaretskii
2002-06-11 13:32 ` 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=Pine.SUN.3.91.1020523075506.25853C-100000@is \
--to=eliz@is.elta.co.il \
--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