Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: tracepoints: Report tracepoint deletions properly
Date: Sat, 27 Oct 2007 09:22:00 -0000	[thread overview]
Message-ID: <1193472863.16917.107.camel@localhost.localdomain> (raw)
In-Reply-To: <m3d4v1flf3.fsf@codesourcery.com>

On Fri, 2007-10-26 at 17:31 -0700, Jim Blandy wrote:
> Committed as obvious.
> 
> I don't think this matters a bit, as there seem to be no clients of
> this particular event, unless I've missed something.

I suspect it was meant for a gui framework that was never written.

Hopefully as a result of your work, people will actually start to 
use tracepoints, and eventually we will want a gui framework for
them.  But I see no reason not to remove them for now, and add
what we really need when we really need it.


> gdb/ChangeLog:
> 2007-10-26  Jim Blandy  <jimb@codesourcery.com>
> 
> 	* tracepoint.c (tracepoint_operation): Report the deletion event
> 	after we have unlinked the tracepoint from the list, and use the
> 	proper tracepoint number.
> 
> diff -r db46634d8623 gdb/tracepoint.c
> --- a/gdb/tracepoint.c	Fri Oct 26 16:39:42 2007 -0700
> +++ b/gdb/tracepoint.c	Fri Oct 26 17:25:51 2007 -0700
> @@ -583,10 +583,11 @@ tracepoint_operation (struct tracepoint 
>        ALL_TRACEPOINTS (t2)
>  	if (t2->next == t)
>  	{
> -	  tracepoint_delete_event (t2->number);
>  	  t2->next = t->next;
>  	  break;
>  	}
> +
> +      tracepoint_delete_event (t->number);
>  
>        if (t->addr_string)
>  	xfree (t->addr_string);


      reply	other threads:[~2007-10-27  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27  1:32 Jim Blandy
2007-10-27  9:22 ` Michael Snyder [this message]

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=1193472863.16917.107.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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