Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/RFC: dump symtab and psymtab lists
Date: Tue, 08 Apr 2003 07:39:00 -0000	[thread overview]
Message-ID: <3E927CAF.1080704@redhat.com> (raw)
In-Reply-To: <vt2y92leuym.fsf@zenia.red-bean.com>

> This patch adds two new commands, 'maint print symtabs' and 'maint
> print psymtabs', that print out the full and partial symtab lists.
> You can supply a regexp to match against the (p)symtab name to just
> list a few.
> 
> The existing 'maint print symbols' and 'maint print psymbols' are
> exhaustive, which is useful sometimes, but they produce so much output
> that they're a pain to use when you just want to see what's up with
> the symtab and psymtab lists themselves.
> 
> The output includes expressions you can cut-and-paste into GDB to get
> a pointer to a specific symtab, psymtab, etc., and it's parenthesized
> to make the Emacs balanced motion commands work usefully.  The
> documentation includes examples.

Jim,

The `maint print' series of commands should all use the syntax:

	(gdb) maint print <component> [ <output-file> ]

(things todo is check that this is consistent).

Andrew


> gdb/ChangeLog:
> 2003-04-07  Jim Blandy  <jimb@redhat.com>
> 
> 	* symmisc.c (maintenance_print_symtabs,
> 	maintenance_print_psymtabs): New functions.
> 	* maint.c (_initialize_maint_cmds): Add commands for the above.
> 	* symtab.h (maintenance_print_symtabs,
> 	maintenance_print_psymtabs): New declarations.
> 	* Makefile.in (symmisc.o): Update dependencies.
> 
> gdb/doc/ChangeLog:
> 2003-04-07  Jim Blandy  <jimb@redhat.com>
> 
> 	* gdb.texinfo (Symbols): Document 'maint print symtabs' and 'maint
> 	print psymtabs'.
> 



  reply	other threads:[~2003-04-08  7:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 23:41 Jim Blandy
2003-04-08  7:39 ` Andrew Cagney [this message]
2003-04-08 17:52   ` Jim Blandy
2003-04-08 21:13     ` Andrew Cagney
2003-04-09  0:09       ` Jim Blandy
2003-04-10  2:10         ` Andrew Cagney
2003-04-10 20:29           ` Jim Blandy
2003-04-10 21:49             ` Andrew Cagney
2003-04-10 21:56               ` Daniel Jacobowitz
2003-04-12  9:34             ` Eli Zaretskii
2003-04-14 18:43               ` Jim Blandy
2003-04-14 18:52                 ` Andrew Cagney
2003-04-14 19:05                   ` David Carlton
2003-04-14 19:27                     ` Andrew Cagney
2003-04-14 22:41                   ` Jim Blandy
2003-04-14 23:40                     ` Andrew Cagney
2003-04-15  1:45                       ` Jim Blandy
2003-04-15 15:49                         ` Andrew Cagney
2003-04-17 22:09                           ` Jim Blandy
2003-04-19  7:40                             ` Eli Zaretskii
2003-05-07 21:43                             ` 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=3E927CAF.1080704@redhat.com \
    --to=ac131313@redhat.com \
    --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