From: Doug Evans <xdje42@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Improve maint print symbols,psymbols,msymbols
Date: Wed, 20 Apr 2016 17:33:00 -0000 [thread overview]
Message-ID: <m38u08rxql.fsf@sspiff.org> (raw)
In-Reply-To: <m3d1pkrxwa.fsf@sspiff.org> (Doug Evans's message of "Wed, 20 Apr 2016 10:30:13 -0700")
Doug Evans <xdje42@gmail.com> writes:
> Hi.
>
> More old sandbox spring cleaning.
>
> At the time I needed this, I used it a lot.
> I've since also added msymbol improvements if only for consistency sake.
> It's helpful to have more control over what to print,
> and to have the output appear on the screen
> without having to go looking for it. Bleah.
>
> 2016-04-20 Doug Evans <xdje42@gmail.com>
>
> * NEWS: Document new syntax for "mt print symbols", "mt print psymbols"
> and "mt print msymbols" commands.
> * psymtab.c (DEV_TTY): Delete.
> (dump_psymtab_addrmap): Don't dump if psymtabs_addrmap is NULL.
> (maintenance_print_psymbols): Rewrite for new syntax:
> mt print psymbols [-objfile objfile] [-pc address] [outfile]
> mt print psymbols [-objfile objfile] [-source source] [outfile]
> (_initialize_psymtab): Update help text.
> * symmisc.c (maintenance_print_symbols): Rewrite for new syntax:
> mt print symbols [-pc address] [outfile]
> mt print symbols [-objfile objfile] [-source source] [outfile]
> (maintenance_print_msymbols): Rewrite for new syntax:
> mt print msymbols [-objfile objfile] [outfile]
> Only print symbols for the current progspace.
> (_initialize_symmisc): Update help text.
>
> doc/
> * gdb.texinfo (Symbols): Update docs for symbol printing maintenance
> commands.
>
> testsuite/
> * gdb.base/maint.exp: Update tests for maint print symbols, psymbols
> and msymbols.
Missed this bit of cleanup that can now be done.
I'll include it when checking in.
--- symmisc.c= 2016-04-20 10:21:41.989332611 -0700
+++ symmisc.c 2016-04-20 10:31:41.049944151 -0700
@@ -40,10 +40,6 @@
#include "psymtab.h"
-#ifndef DEV_TTY
-#define DEV_TTY "/dev/tty"
-#endif
-
/* Unfortunately for debugging, stderr is usually a macro. This is painful
when calling functions that take FILE *'s from the debugger.
So we make a variable which has the same value and which is accessible when
next prev parent reply other threads:[~2016-04-20 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 17:30 Doug Evans
2016-04-20 17:33 ` Doug Evans [this message]
2016-04-20 17:45 ` Eli Zaretskii
2016-04-22 13:31 ` Pedro Alves
2016-12-19 18:04 ` Doug Evans
2016-12-20 12:52 ` Pedro Alves
2016-12-22 23:53 ` Doug Evans
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=m38u08rxql.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).