From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21215 invoked by alias); 22 Oct 2007 18:56:37 -0000 Received: (qmail 21207 invoked by uid 22791); 22 Oct 2007 18:56:37 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 22 Oct 2007 18:56:31 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0F8572AA642 for ; Mon, 22 Oct 2007 14:56:30 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bO2UeOxgWyEj for ; Mon, 22 Oct 2007 14:56:30 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id C70892A976C for ; Mon, 22 Oct 2007 14:56:29 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id C61F8E7AC8; Mon, 22 Oct 2007 11:56:27 -0700 (PDT) Date: Mon, 22 Oct 2007 19:30:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: Re: [RFC] Support exec tracing on GNU/Linux and HP-UX Message-ID: <20071022185627.GH764@adacore.com> References: <20071019175920.GA548@caradoc.them.org> <20071022043831.GD764@adacore.com> <20071022114328.GA1421@caradoc.them.org> <20071022184702.GG764@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071022184702.GG764@adacore.com> User-Agent: Mutt/1.4.2.2i 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: 2007-10/txt/msg00516.txt.bz2 > It makes sense to do the same on HP/UX as well. It shouldn't be > very difficult, and I have a 30min window right now, so I'll give > it a shot. Actually, not so simple, because the EXEC event counts as one of the 2 events we expect during the startup phase. So the EXEC events must be activated at startup-time. The only option I can see at this point is to add a static global that is set during the startup phase, and would then cause the EXEC event to be translated into a SIGTRAP vulgaris when set. Another approach would be to have infrun treat EXEC events as SIGTRAPs during the startup phase. I don't think the second option is easier to implement (infrun needs to find out whether we're in the middle of startup or not, and then we need to redirect EXEC events into SIGTRAP events). What do you think of option 1? -- Joel