From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay1.mentorg.com (relay1.mentorg.com [192.94.38.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "relay1.mentorg.com", Issuer "Entrust Certification Authority - L1B" (not verified)) by ozlabs.org (Postfix) with ESMTPS id D9A1F2C0084 for ; Sat, 4 Aug 2012 02:02:42 +1000 (EST) Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1SxK7c-0002Ne-8Q from Luis_Gustavo@mentor.com for linuxppc-dev@lists.ozlabs.org; Fri, 03 Aug 2012 08:49:04 -0700 Message-ID: <501BF2FC.8020309@mentor.com> Date: Fri, 03 Aug 2012 12:49:16 -0300 From: Luis Gustavo MIME-Version: 1.0 To: linuxppc-dev@lists.ozlabs.org Subject: Threads inheriting debug state from parent threads Content-Type: text/plain; charset=ISO-8859-1; format=flowed Reply-To: "Gustavo, Luis" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, I'm actually chasing a problem with GDB and hw watchpoints for embedded ppc targets. If a thread X creates thread Y, is it expected that thread Y will inherit all the debug state from thread X? Including, for example, any hardware watchpoints/breakpoints that are set in thread X? Thanks, Luis