Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Add fullname field for MI -break-info command
Date: Tue, 24 Jan 2006 16:42:00 -0000	[thread overview]
Message-ID: <200601241932.16022.ghost@cs.msu.su> (raw)

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


Hello!

The attached patch adds the "fullname" field to the output of MI -break-info
command.

Changelog entry:

2006-01-24 Vladimir Prus <ghost@cs.msu.su>
        
        * breakpoint.c (print_one_breakpoint): For MI-like UI, output
         'fullname' field.

Patch attached.

- Volodya

[-- Attachment #2: break_info_fullname.diff --]
[-- Type: text/x-diff, Size: 944 bytes --]

Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.220
diff -u -r1.220 breakpoint.c
--- breakpoint.c	16 Jan 2006 12:55:18 -0000	1.220
+++ breakpoint.c	24 Jan 2006 15:10:47 -0000
@@ -3603,6 +3603,23 @@
       print_command_lines (uiout, l, 4);
       do_cleanups (script_chain);
     }
+
+  if (ui_out_is_mi_like_p (uiout))
+    {
+      if (b->loc->loc_type == bp_loc_software_breakpoint || 
+          b->loc->loc_type == bp_loc_hardware_watchpoint)
+        {
+          struct symtab_and_line sal = find_pc_line (b->loc->address, 0);
+          symtab_to_fullname (sal.symtab);
+
+          if (sal.symtab->fullname)
+            {
+              annotate_field(10);
+              ui_out_field_string (uiout, "fullname", sal.symtab->fullname);
+            }
+        }
+    }
+
   do_cleanups (bkpt_chain);
   do_cleanups (old_chain);
 }

             reply	other threads:[~2006-01-24 16:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 16:42 Vladimir Prus [this message]
2006-01-24 16:51 ` Bob Rossi
2006-01-25 11:07   ` Vladimir Prus
2006-01-25 12:10     ` Bob Rossi
2006-01-25 12:37       ` Andreas Schwab
2006-01-25 12:50       ` Vladimir Prus
2006-01-25 13:45         ` Bob Rossi
2006-01-26  7:10           ` Vladimir Prus
2006-01-28 13:10   ` Vladimir Prus
2006-02-01 22:32     ` Daniel Jacobowitz
2006-02-02  7:07       ` Vladimir Prus
2006-02-06 21:55         ` Daniel Jacobowitz
2006-01-24 21:13 ` Daniel Jacobowitz
2006-01-25 13:31   ` Vladimir Prus
2006-01-25 13:46     ` Bob Rossi
2006-01-26  7:20       ` Vladimir Prus
2006-01-25 13:51     ` Daniel Jacobowitz
2006-01-25 17:56     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2006-01-26 11:27 Nick Roberts
2006-01-26 11:44 ` Vladimir Prus
2006-01-26  7:13 Nick Roberts
2006-01-26  7:06 Nick Roberts
2006-01-24 16:42 Vladimir Prus

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=200601241932.16022.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.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