From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10655 invoked by alias); 24 Oct 2007 15:10:01 -0000 Received: (qmail 10634 invoked by uid 22791); 24 Oct 2007 15:10:00 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_20,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO,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; Wed, 24 Oct 2007 15:09:58 +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.1) with ESMTP id l9OF9uVp028178 for ; Wed, 24 Oct 2007 11:09:56 -0400 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 l9OF9ub0030985 for ; Wed, 24 Oct 2007 11:09:56 -0400 Received: from localhost.localdomain (vpn-14-190.rdu.redhat.com [10.11.14.190]) by pobox-2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l9OF9tTZ030408 for ; Wed, 24 Oct 2007 11:09:55 -0400 Message-ID: <471F603F.2090703@redhat.com> Date: Wed, 24 Oct 2007 15:10:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: Frysk Hackers Subject: TaskState handleTrappedEvent Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2007-q4/txt/msg00067.txt.bz2 I noticed that this state is getting a little more crowded and will be even more crowded soon with watchpoints. Before I add my own patches here, some questions: 1) Is there an important order precedence here? Must it handle single step over breakpoints over watchpoints in any particular order? I can't think of why the order matters. 2) I'm a little fuzzy on if there were will be an opportunity for multiple events to happen on a single sigtrap (ie breakpoint and watchpoint). I cannot think of any right now other than single step writing something to a memory address that the watchpoint is monitoring, but that should be caught on as another later sigtrap. Are there opportunities for multiple events? If so, are there any precedence issues? Regards Phil