Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
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: Wed, 01 Feb 2006 22:32:00 -0000	[thread overview]
Message-ID: <20060201223232.GB14187@nevyn.them.org> (raw)
In-Reply-To: <drfqem$kni$1@sea.gmane.org>

On Sat, Jan 28, 2006 at 04:09:42PM +0300, Vladimir Prus wrote:
> Revised patch attached. I did verify that it causes no regressions for MI
> tests.
> 
> 
> Note, however, that I could not verify that it does not cause any
> regressions globally, because something seems wrong with my configuration
> or the test system. Sporadically, I get errors like this:

What system are you testing on?  Presumably a bug in the host or in the
port of expect to the host.

I've verified no regressions on x86_64-pc-linux-gnu.

The patch looks OK.  There's a couple of formatting errors, and
it needs ChangeLog entries, and then it can be applied.

Oh, and Nick was right: you don't need the loc_type check any more.
Everything in that case statement will be a breakpoint and have
a valid address.

> +                struct symtab_and_line sal = find_pc_line (b->loc->address, 0);
> +                char* fullname = symtab_to_fullname (sal.symtab);

char *fullname, please, for consistency.

> +                if (fullname)
> +                  {
> +                    ui_out_field_string (uiout, "fullname", fullname);
> +                  }

Don't need the extra braces here.

> @@ -75,25 +78,27 @@
>      # -break-insert -t srcfile:$line_callee4_head
>      # -break-list
>  
> +
> +
>      mi_gdb_test "222-break-insert -t main" \
> -             "222\\^done,bkpt=\{number=\"1\",type=\"breakpoint\",disp=\"del\",enabled=\"y\",addr=\"$hex\",func=\"main\",file=\".*basics.c\",line=\"$line_main_body\",times=\"0\"\}" \
> +             "222\\^done,bkpt=\{number=\"1\",type=\"breakpoint\",disp=\"del\",enabled=\"y\",addr=\"$hex\",func=\"main\",file=\".*basics.c\",${fullname},line=\"$line_main_body\",times=\"0\"\}" \
>               "break-insert -t operation"

And don't need the extra blank lines.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-02-01 22:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2006-01-24 16:42 Vladimir Prus
2006-01-26  7:06 Nick Roberts
2006-01-26  7:13 Nick Roberts
2006-01-26 11:27 Nick Roberts
2006-01-26 11:44 ` 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=20060201223232.GB14187@nevyn.them.org \
    --to=drow@false.org \
    --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