Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] "maint print psymbols" with large section tables
Date: Thu, 01 Mar 2001 00:47:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010301104141.4534I-100000@is> (raw)
In-Reply-To: <200102282148.NAA06598@bosch.cygnus.com>

On Wed, 28 Feb 2001, Michael Elizabeth Chastain wrote:

> This patch fixes "maint print psymbols" to work better with large
> section offset tables.  The existing code prints the whole section offset
> tale all on one line, which is awkward when a section offset table has
> 900+ entries.  (The code thinks it is wrapping lines, but wrap_here()
> does no good when all the output is going to outfile).
> 
> The existing code also takes so long to execute that I saw timeout
> failures in gdb.base/maint.exp.  This is my motivation for changing
> the code.
> 
> The new code prints only the non-zero entries of a section offset table,
> one per line.

I don't like removing features, unless we know for a fact that no one
uses them.  In my experience, many times a feature is requested
shortly after it is removed ;-)

Is it possible that someone would want to see the zero entries as
well?  If so, I think we should at least leave behind some option that
could be used to see all the entries, albeit in a different format
(one per line).

Also, if this patch is accepted, please update the docs of "maint print 
psymbols" in gdb.texinfo.  It should at least say that zero entries are 
skipped.


  reply	other threads:[~2001-03-01  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28 13:48 Michael Elizabeth Chastain
2001-03-01  0:47 ` Eli Zaretskii [this message]
2001-03-01  7:40   ` Andrew Cagney
2001-03-01 12:44 Michael Elizabeth Chastain

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.1010301104141.4534I-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=chastain@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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