Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	       "Dr. David Alan Gilbert" <dave@treblig.org>
Subject: Re: [PATCH] Fix for PR 15413 (segfault when completing "condition" for pending bp)
Date: Tue, 07 May 2013 16:16:00 -0000	[thread overview]
Message-ID: <518928F2.4080507@redhat.com> (raw)
In-Reply-To: <m3li7rqwzt.fsf@redhat.com>

On 05/07/2013 04:39 AM, Sergio Durigan Junior wrote:

> -	for (loc = b->loc; loc; loc = loc->next)
> -	  {
> -	    char location[50];
> -
> -	    if (single)
> -	      xsnprintf (location, sizeof (location), "%d", b->number);
> -	    else
> -	      xsnprintf (location, sizeof (location),  "%d.%d", b->number,
> -			 count);
> +	{
> +	  char location[50];

This is no longer a location.  So s/location/number/g.

>  
> +# Complete the condition (PR 15413).
> +# This test must come right after we set the first pending breakpoint, and
> +# before we set any other breakpoint, since we are testing if the "condition"
> +# command can properly complete its argument.  The PR only fails if there
> +# is only one pending breakpoint set (without anything else).

This last sentence isn't right.  You only need a pending breakpoint to
trigger the crash, it doesn't matter how many breakpoints you have.

> +gdb_test "complete condition " "condition 1"

OK with these fixed, mainline and 7.6.

Thanks,
-- 
Pedro Alves


  reply	other threads:[~2013-05-07 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  2:59 Sergio Durigan Junior
2013-05-06 17:49 ` Pedro Alves
2013-05-06 20:57   ` Sergio Durigan Junior
2013-05-06 21:08     ` Pedro Alves
2013-05-07  3:39       ` Sergio Durigan Junior
2013-05-07 16:16         ` Pedro Alves [this message]
2013-05-07 17:06           ` Sergio Durigan Junior

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=518928F2.4080507@redhat.com \
    --to=palves@redhat.com \
    --cc=dave@treblig.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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