Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add fullname field for MI -break-info command
Date: Thu, 26 Jan 2006 11:27:00 -0000	[thread overview]
Message-ID: <17368.45539.671403.826516@kahikatea.snap.net.nz> (raw)

+  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)
                                               ^^^^^^^^^^
Should this be bp_loc_hardware_breakpoint?

+        {
+          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);
+            }
+        }
+    }
+

Also, I would move it up breakpoint.c (without the call to annotate_field)
to here:

	if (b->source_file)
	  {
	    sym = find_pc_sect_function (b->loc->address, b->loc->section);
	    if (sym)
	      {
		ui_out_text (uiout, "in ");
		ui_out_field_string (uiout, "func",
				     SYMBOL_PRINT_NAME (sym));
		ui_out_wrap_hint (uiout, wrap_indent);
		ui_out_text (uiout, " at ");
	      }
	    ui_out_field_string (uiout, "file", b->source_file);
	    ui_out_text (uiout, ":");

--->

	    ui_out_field_int (uiout, "line", b->line_number);
	  }

to be consistent with the output of print_frame, where the order is
file, fullname, line.

Putting it here might also mean that the test for b->loc->loc_type isn't
needed, but I don't really know.


Nick                                           http://www.inet.net.nz/~nickrob


             reply	other threads:[~2006-01-26 11:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 11:27 Nick Roberts [this message]
2006-01-26 11:44 ` Vladimir Prus
  -- strict thread matches above, loose matches on Subject: below --
2006-01-26  7:13 Nick Roberts
2006-01-26  7:06 Nick Roberts
2006-01-24 16:42 Vladimir Prus
2006-01-24 16:42 Vladimir Prus
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

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=17368.45539.671403.826516@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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