From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6123 invoked by alias); 4 Dec 2003 21:01:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6098 invoked from network); 4 Dec 2003 21:01:23 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 4 Dec 2003 21:01:23 -0000 Received: by localhost.redhat.com (Postfix, from userid 469) id F2ED61A42DB; Thu, 4 Dec 2003 16:01:22 -0500 (EST) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16335.41122.634794.412421@localhost.redhat.com> Date: Thu, 04 Dec 2003 21:01:00 -0000 To: "Newman, Mark (N-Superior Technical Resource Inc)" Cc: Mark Newman , gdb@sources.redhat.com Subject: RE: async operation In-Reply-To: References: X-SW-Source: 2003-12/txt/msg00087.txt.bz2 Newman, Mark (N-Superior Technical Resource Inc) writes: > IMHO async is not an invention of the client but the manner in which gdb > controls the client. ;-) > > I am attaching a gdb output with remote_debug set. In this instance the > sequence > > > interrupt > > cont & > > worked once but did not work the second time. [...] > > It may be my changes that are causing the problem. Can you try on a gdb w/o your modifications? > > Program received signal SIGINT, Interrupt. > Sending packet: $M4000acb0,1:55#68...Ack > Packet received: ENN > Sending packet: $M4000acb0,1:55#68...Ack > Packet received: ENN > Sending packet: $mbffff830,4#62...Ack > Packet received: 55320000 > Sending packet: $mbffff834,4#66...Ack > Packet received: 55320000 > 0x080483f7 in main (argc=12885, argv=0x3255) at main.c:52 > 52 while (j < 1000000) { I assume you said continue here? > > Sending packet: $c#63...Ack > > remote_stop called Hmm do you see any output that says that remote_interrupt has been called as well? I wonder if the signal handlers are screwed up. > > Sending packet: $c#63...Packet instead of Ack, ignoring it gdb keeps issuing the continue command for some reason. maybe it hasn't realized that the target is actually running. elena