Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: msnyder@redhat.com
Cc: Keith Seitz <keiths@redhat.com>,
	msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix gdb/669 (fwd)
Date: Tue, 05 Nov 2002 14:42:00 -0000	[thread overview]
Message-ID: <15816.18511.514241.635599@localhost.redhat.com> (raw)
In-Reply-To: <15797.46515.614922.970446@localhost.redhat.com>

Elena Zannoni writes:
 > Keith Seitz writes:
 >  > Ping.
 >  > 
 >  > ---------- Forwarded message ----------
 >  > Date: Tue, 24 Sep 2002 12:42:24 -0700 (PDT)
 >  > From: Keith Seitz <keiths@redhat.com>
 >  > To: gdb-patches@sources.redhat.com
 >  > Subject: [RFA] Fix gdb/669
 >  > 
 >  > Hi,
 >  > 
 >  > This patch fixes gdb/669, which demonstrates that the MI command 
 >  > "thread-list-ids" and the console's "info thread" get out of sync.
 >  > 
 >  > This is caused by the MI command not following the console command, which 
 >  > prunes old threads and looks for new ones when it is called.
 >  > 
 > 
 > 
 > Even though this code is in thread.c, which is Michael's domain, it is
 > only used from mi. It looks right to me.
 > 
 > Michael?
 > 

Can this be committed? It is a piece of the MI branch merge.



 > Elena
 > 
 > 
 >  > Keith
 >  > 
 >  > ChangeLog
 >  > 2002-09-05  Keith Seitz  <keiths@redhat.com>
 >  > 
 >  > 	* thread.c (do_captured_list_thread_ids): Call prune_threads and
 >  > 	target_find_new_threads.
 >  > 
 >  > Patch
 >  > Index: thread.c
 >  > ===================================================================
 >  > RCS file: /cvs/src/src/gdb/thread.c,v
 >  > retrieving revision 1.23
 >  > diff -p -r1.23 thread.c
 >  > *** thread.c	2 Aug 2002 20:51:21 -0000	1.23
 >  > --- thread.c	24 Sep 2002 19:32:40 -0000
 >  > *************** do_captured_list_thread_ids (struct ui_o
 >  > *** 262,267 ****
 >  > --- 262,269 ----
 >  >     struct thread_info *tp;
 >  >     int num = 0;
 >  >   
 >  > +   prune_threads ();
 >  > +   target_find_new_threads ();
 >  >     ui_out_tuple_begin (uiout, "thread-ids");
 >  >   
 >  >     for (tp = thread_list; tp; tp = tp->next)
 >  > 


  reply	other threads:[~2002-11-05 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 11:00 Keith Seitz
2002-10-22 13:34 ` Elena Zannoni
2002-11-05 14:42   ` Elena Zannoni [this message]
2002-11-07  7:02 ` Elena Zannoni
2002-11-08 12:07   ` Mark Kettenis
2002-12-19 20:29     ` Elena Zannoni
2002-12-19 21:57 Michael Elizabeth Chastain
2002-12-20  6:50 ` Elena Zannoni
2002-12-22 15:54 Michael Elizabeth Chastain

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=15816.18511.514241.635599@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@redhat.com \
    --cc=msnyder@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