Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Josef Ezra <sgdb@subdimension.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Josef Ezra <jezra@emc.com>, gdb-patches@sources.redhat.com
Subject: Re: Request for new gdb command: 'info orientation'
Date: Thu, 13 Jun 2002 11:20:00 -0000	[thread overview]
Message-ID: <3D08E29B.1000609@subdimension.com> (raw)
In-Reply-To: <3D08DB87.A8119A1D@redhat.com>

Michael Snyder wrote:
> Josef Ezra wrote:
> 
>>Hi all
>>
>>While writing a perl gui for gdb, I had to add a new command. It looks
>>like this:
>>
>>(gdb) info orientation main
>>0x00034960:753
>>0x00034b44:757
>>0x00034b48:761
>>0x00034b50:759
>>0x00034b54:761
>>0x00034b68:763
>>0x00034b70:772
>>(gdb)
>>
>>and associate addresses with line numbers. This information allow
>>merging the disassemble with the sources without executing 'info line'
>>command for each address, since the last took too long (the difference
>>between O(n^2) to O(n)).
>>(The command was also useful for analyzing patches and code changes.)
> 
> 
> I like it as maybe a maintainer command (or even a user one, if
> you think users might gain something from it.
> 
> I don't like the name, though -- "info orientation" doesn't say
> anything to me.  Maybe "info lines"?  Or, as a maintainer command, 
> "info sal"?
> 

How about 'maintenance info-lines'?



  reply	other threads:[~2002-06-13 18:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  8:11 should gdb require '.text' and '.data' sections? josef ezra
2002-04-18 11:15 ` Michael Snyder
2002-04-22  6:32   ` Josef Ezra
2002-04-24  6:45   ` [RFA] " Josef Ezra
2002-06-13 10:06   ` Request for new gdb command: 'info orientation' Josef Ezra
2002-06-13 10:35     ` Andrew Cagney
2002-06-13 11:06     ` Michael Snyder
2002-06-13 11:20       ` Josef Ezra [this message]
2002-06-17 12:34       ` [RFA] new command: 'maintenance info lines' Josef Ezra
2002-06-17 22:26         ` Eli Zaretskii
2002-06-18 13:47           ` josef ezra
2002-06-18 14:42             ` Michael Snyder
2002-06-18 22:42             ` Eli Zaretskii
2002-06-19  7:27               ` Josef Ezra
2002-06-18 14:35         ` Michael Snyder
2002-09-06  5:08           ` Josef Ezra
2002-09-18 22:33             ` Eli Zaretskii
2002-09-23  8:06               ` Josef Ezra
2002-09-23 22:12                 ` Eli Zaretskii
2002-09-25 13:26             ` Fernando Nasser
2002-09-26  6:49               ` Josef Ezra
2002-09-26 10:45                 ` Fernando Nasser
2002-09-26 19:03                   ` Andrew Cagney
2002-09-06 13:44           ` Josef Ezra

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=3D08E29B.1000609@subdimension.com \
    --to=sgdb@subdimension.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jezra@emc.com \
    --cc=msnyder@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