From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14311 invoked by alias); 15 Jun 2008 21:49:11 -0000 Received: (qmail 14301 invoked by uid 22791); 15 Jun 2008 21:49:10 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 15 Jun 2008 21:48:46 +0000 Received: from HOME-C4E4A596F7 ([84.228.242.237]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K2I009TLYKQAOG0@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Mon, 16 Jun 2008 01:02:57 +0300 (IDT) Date: Sun, 15 Jun 2008 22:18:00 -0000 From: Eli Zaretskii Subject: Re: [non-stop] 01/10 Add "executing" property In-reply-to: <200806152203.14626.pedro@codesourcery.com> X-012-Sender: halo1@inter.net.il To: Pedro Alves Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8BIT References: <200806152203.14626.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00290.txt.bz2 > From: Pedro Alves > Date: Sun, 15 Jun 2008 22:03:14 +0100 > > The "running" thread property recently added represents the frontend view > of the thread running state. While doing a step for instance, the inferior > starts/stops several times while single-stepping.  We only clear > the "running" state of the inferior when it does a normal_stop. > This patch adds a new field, that altough similar to "running" > has a different usage.  It replaces the current target_executing > global with a similar per-thread concept.  Inferior and frame/stack > control then can then use this property to know when it is possible > to read registers and memory from a thread. Thanks, but isn't any of the significant changes in these series of patches worthy of being mentioned in gdbint.texinfo? > * Makefile.in (event-top.o, frame.o, inf-loop.o, top.o): > Update. I think you should tell what prerequisites were added to each target. A simple "update" will never reveal when a prerequisite was added, if someone will ever want to know.