Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: make `info source' say whether macro info is present
Date: Thu, 23 May 2002 13:57:00 -0000	[thread overview]
Message-ID: <npelg2pr3z.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020523075506.25853C-100000@is>


Eli Zaretskii <eliz@is.elta.co.il> writes:

> 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.

*blush*  Thanks.  This patch includes a doc fix:

gdb/ChangeLog:
2002-05-22  Jim Blandy  <jimb@redhat.com>

	* source.c (source_info): Mention whether the symtab has
	information about preprocessor macros.

gdb/testsuite/ChangeLog:
2002-05-22  Jim Blandy  <jimb@redhat.com>

	* lib/gdb.exp (get_debug_format): Tolerate message saying whether
	preprocessor macro information is present.

gdb/doc/ChangeLog:
2002-05-23  Jim Blandy  <jimb@redhat.com>

	* gdb.texinfo (Symbols): Update documentation for `info source'
	command.

Index: gdb/source.c
===================================================================
RCS file: /cvs/src/src/gdb/source.c,v
retrieving revision 1.28
diff -c -r1.28 source.c
*** gdb/source.c	23 Apr 2002 11:09:09 -0000	1.28
--- gdb/source.c	23 May 2002 20:02:33 -0000
***************
*** 500,505 ****
--- 500,507 ----
  
    printf_filtered ("Source language is %s.\n", language_str (s->language));
    printf_filtered ("Compiled with %s debugging format.\n", s->debugformat);
+   printf_filtered ("%s preprocessor macro info.\n",
+                    s->macro_table ? "Includes" : "Does not include");
  }
  \f
  
Index: gdb/testsuite/lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.18
diff -c -r1.18 gdb.exp
*** gdb/testsuite/lib/gdb.exp	10 May 2002 18:38:09 -0000	1.18
--- gdb/testsuite/lib/gdb.exp	23 May 2002 20:02:34 -0000
***************
*** 1435,1441 ****
      set debug_format "unknown"
      send_gdb "info source\n"
      gdb_expect 10 {
! 	-re "Compiled with (.*) debugging format.\r\n$gdb_prompt $" {
  	    set debug_format $expect_out(1,string)
  	    verbose "debug format is $debug_format"
  	    return 1;
--- 1435,1441 ----
      set debug_format "unknown"
      send_gdb "info source\n"
      gdb_expect 10 {
! 	-re "Compiled with (.*) debugging format.\r\n.*$gdb_prompt $" {
  	    set debug_format $expect_out(1,string)
  	    verbose "debug format is $debug_format"
  	    return 1;
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.100
diff -c -r1.100 gdb.texinfo
*** gdb/doc/gdb.texinfo	17 May 2002 18:00:03 -0000	1.100
--- gdb/doc/gdb.texinfo	23 May 2002 20:02:45 -0000
***************
*** 9020,9028 ****
  
  @kindex info source
  @item info source
! Show the name of the current source file---that is, the source file for
! the function containing the current point of execution---and the language
! it was written in.
  
  @kindex info sources
  @item info sources
--- 9020,9044 ----
  
  @kindex info source
  @item info source
! Show information about the current source file---that is, the source file for
! the function containing the current point of execution:
! @itemize @bullet
! @item
! the name of the source file, and the directory containing it,
! @item
! the directory it was compiled in,
! @item
! its length, in lines,
! @item
! which programming language it is written in,
! @item
! whether the executable includes debugging information for that file, and
! if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and
! @item
! whether the debugging information includes information about
! preprocessor macros.
! @end itemize
! 
  
  @kindex info sources
  @item info sources




  reply	other threads:[~2002-05-23 20:05 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
2002-05-23 13:57   ` Jim Blandy [this message]
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=npelg2pr3z.fsf@zwingli.cygnus.com \
    --to=jimb@redhat.com \
    --cc=eliz@is.elta.co.il \
    --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