From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21871 invoked by alias); 17 Nov 2005 19:52:32 -0000 Received: (qmail 21859 invoked by uid 22791); 17 Nov 2005 19:52:30 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 17 Nov 2005 19:52:30 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id jAHJqTeI003498 for ; Thu, 17 Nov 2005 14:52:29 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id jAHJqOV00305 for ; Thu, 17 Nov 2005 14:52:24 -0500 Received: from localhost.localdomain (vpn50-163.rdu.redhat.com [172.16.50.163]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id jAHJqN7J011420 for ; Thu, 17 Nov 2005 14:52:23 -0500 Received: from ironwood.lan (ironwood.lan [192.168.64.8]) by localhost.localdomain (8.12.11/8.12.10) with ESMTP id jAHJqIPN016266 for ; Thu, 17 Nov 2005 12:52:18 -0700 Date: Thu, 17 Nov 2005 19:52:00 -0000 From: Kevin Buettner To: gdb@sources.redhat.com Subject: Re: Interrupting remote targets from GDB Message-ID: <20051117125217.0a503b4e@ironwood.lan> In-Reply-To: <20051117185056.GA18702@nevyn.them.org> References: <20051117112043.4d9f587e@ironwood.lan> <20051117185056.GA18702@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00352.txt.bz2 On Thu, 17 Nov 2005 13:50:56 -0500 Daniel Jacobowitz wrote: > Fine by me; can we also add a word about what to do with interrupts > when the target is stopped? I believe they should be dropped rather > than responded to, per conversation on gdb@ earlier this month. I've added one sentence to the text I posted earlier. Here's the revised text: When a program on the remote target is running, GDB may attempt to interrupt it by sending a `Ctrl-C' or a BREAK, control of which is specified via GDB's `remotebreak' setting. The precise meaning of BREAK is defined by the transport mechanism and may, in fact, be undefined. `Ctrl-C', on the other hand, is defined for all transport mechanisms and is represented by sending the single byte 0x03. `Ctrl-C' must not be sent as part of a packet as defined in the "Overview". Stubs are not required to recognize these interrupt mechanisms and the precise meaning associated with receipt of the interrupt is implementation defined. If the stub is successful at interrupting the running program, it is expected that it will send one of the `Stop Reply Packets' to GDB as a result of successfully stopping the program. Interrupts received while the program is stopped will be discarded.