From: "josef ezra" <jezra@emc.com>
To: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: "Michael Snyder" <msnyder@redhat.com>, <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] new command: 'maintenance info lines'
Date: Tue, 18 Jun 2002 13:47:00 -0000 [thread overview]
Message-ID: <022e01c21709$69a4aea0$ad219fa8@lss.emc.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020618082315.16082D-100000@is>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
Eli Zaretskii wrote:
>
> On Mon, 17 Jun 2002, Josef Ezra wrote:
>
> > Following the line of 'maintenance info breakpoints / sections /
> > sol-threads' commands, I'd like to suggest 'maintenance info lines' for
> > this line-address dump.
> >
> > - jezra
> >
> > * printcmd.c (maintenance_info_lines): created
> > (_initialize_printcmd): add command
>
> Please also consider adding a suitable description to gdb.texinfo.
> TIA
>
I'm adding this gdb.textinfo entry (should I re-commit the whole thing?)
- jezra
[-- Attachment #2: diff --]
[-- Type: application/octet-stream, Size: 766 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.102
diff -u -3 -r1.102 gdb.texinfo
--- gdb.texinfo 11 Jun 2002 20:36:57 -0000 1.102
+++ gdb.texinfo 18 Jun 2002 20:40:29 -0000
@@ -4360,6 +4360,13 @@
can set @var{instruction-set} to either @code{intel} or @code{att}.
The default is @code{att}, the AT&T flavor used by default by Unix
assemblers for x86-based targets.
+
+@kindex maint info lines
+@item maint info lines
+This command takes same parameters as @code{disassemble}, but only
+dumps an 'address:line' pairs. Every pair means: "from this address
+to the next pair, the code was generated by that line".
+
@end table
next prev parent reply other threads:[~2002-06-18 20:47 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
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 [this message]
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='022e01c21709$69a4aea0$ad219fa8@lss.emc.com' \
--to=jezra@emc.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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