From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5806 invoked by alias); 26 Feb 2008 15:14:07 -0000 Received: (qmail 5795 invoked by uid 22791); 26 Feb 2008 15:14:05 -0000 X-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_50,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 26 Feb 2008 15:13:43 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m1QFDgI1003664 for ; Tue, 26 Feb 2008 10:13:42 -0500 Received: from pobox-2.corp.redhat.com (pobox-2.corp.redhat.com [10.11.255.15]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m1QFDfoE031218 for ; Tue, 26 Feb 2008 10:13:41 -0500 Received: from localhost.localdomain (vpn-6-15.fab.redhat.com [10.33.6.15]) by pobox-2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m1QFDdVt028836 for ; Tue, 26 Feb 2008 10:13:40 -0500 Message-ID: <47C42CA3.1030003@redhat.com> Date: Tue, 26 Feb 2008 15:14:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Frysk Hackers Subject: Watchpoint prorogation to child threads Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00072.txt.bz2 A question about watchpoint prorogation to child threads: Thread A clones/forks Thread B In the state machine that deals with the watchpoint code, the new code will update cloned offspring with the same set of watchpoints. This is how I see it now. Are there useful use-cases that dictate that this behavior should not happen? Regards Phil