Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Josef Ezra <jezra@emc.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Josef Ezra <jezra@emc.com>, gdb-patches@sources.redhat.com
Subject: [RFA] new command: 'maintenance info lines'
Date: Mon, 17 Jun 2002 12:34:00 -0000	[thread overview]
Message-ID: <3D0E39E6.5060701@emc.com> (raw)
In-Reply-To: <3D08DB87.A8119A1D@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

Michael Snyder wrote:
> 
> 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"?
> 



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


[-- Attachment #2: m-i-lines.patch --]
[-- Type: text/plain, Size: 3185 bytes --]

Index: printcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/printcmd.c,v
retrieving revision 1.39
diff -u -5 -r1.39 printcmd.c
--- printcmd.c	11 May 2002 23:48:23 -0000	1.39
+++ printcmd.c	17 Jun 2002 18:36:58 -0000
@@ -2383,10 +2383,79 @@
 
   return TARGET_PRINT_INSN (memaddr, TARGET_PRINT_INSN_INFO);
 }
 \f
 
+/*
+  Print range as 'Address:Line' pairs. This command might be usefull
+  to associate sources and assembly commands. 
+*/
+
+static void
+maintenance_info_lines (char *arg, int from_tty)
+{
+  CORE_ADDR low, high;
+  {
+    char *name;
+    CORE_ADDR pc, pc_masked;
+    char *space_index;
+    name = NULL;
+    if (!arg)
+      {
+        if (!selected_frame)
+          error ("No frame selected.\n");
+
+        pc = get_frame_pc (selected_frame);
+        if (find_pc_partial_function (pc, &name, &low, &high) == 0)
+          error ("No function contains program counter for selected frame.\n");
+
+        low += FUNCTION_START_OFFSET;
+      }
+    else if (!(space_index = (char *) strchr (arg, ' ')))
+      {
+        /* One argument.  */
+        pc = parse_and_eval_address (arg);
+        if (find_pc_partial_function (pc, &name, &low, &high) == 0)
+          error ("No function contains specified address.\n");
+        low += FUNCTION_START_OFFSET;
+      }
+    else
+      {
+        /* Two arguments.  */
+        *space_index = '\0';
+        low = parse_and_eval_address (arg);
+        high = parse_and_eval_address (space_index + 1);
+      }
+  }
+  /* OK, we got the low-high range, what now? */
+  {
+    struct symtab *symtab ;
+    struct linetable_entry *le ;
+    int i, nitems ;
+    symtab = find_pc_symtab (low ) ;
+    if (symtab && symtab->linetable) 
+      {
+    
+        le = symtab->linetable->item ;
+        nitems = symtab->linetable->nitems ;
+
+                                /* skip to low */
+        for (i = 0 ; 
+             (i < nitems - 1) && (le[i + 1].pc < low) ; 
+             i++ ) ;
+
+                                /* and print all the way to high */
+        for (; (i < nitems -1) && (le[i].pc <= high); i++ )
+          {
+            if (le[i].pc   != le[i+1].pc   ) 
+                                /* optimized line ? */
+              printf_filtered ("0x%08x:%d\n", (unsigned) le[i].pc, le[i].line ) ;
+          }
+      }
+  }
+}
+
 void
 _initialize_printcmd (void)
 {
   struct cmd_list_element *c;
 
@@ -2561,7 +2630,13 @@
 
   examine_b_type = init_type (TYPE_CODE_INT, 1, 0, "examine_b_type", NULL);
   examine_h_type = init_type (TYPE_CODE_INT, 2, 0, "examine_h_type", NULL);
   examine_w_type = init_type (TYPE_CODE_INT, 4, 0, "examine_w_type", NULL);
   examine_g_type = init_type (TYPE_CODE_INT, 8, 0, "examine_g_type", NULL);
+  add_cmd ( "lines", class_maintenance, maintenance_info_lines,
+            concat ("Dump a line-address table a specified section of memory.\n\
+Default is the function surrounding the pc of the selected frame.\n\
+With a single argument, the function surrounding that address is dumped.\n\
+Two arguments are taken as a range of memory to dump.", NULL ), 
+            &maintenanceinfolist) ; 
 
 }

  parent reply	other threads:[~2002-06-17 19:34 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       ` Josef Ezra [this message]
2002-06-17 22:26         ` [RFA] new command: 'maintenance info lines' 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=3D0E39E6.5060701@emc.com \
    --to=jezra@emc.com \
    --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