From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14368 invoked by alias); 18 Nov 2003 15:50:38 -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 14361 invoked from network); 18 Nov 2003 15:50:37 -0000 Received: from unknown (HELO mailgw3a.lmco.com) (192.35.35.7) by sources.redhat.com with SMTP; 18 Nov 2003 15:50:37 -0000 Received: from emss04g01.ems.lmco.com ([166.17.13.122]) by mailgw3a.lmco.com (8.11.6p2/8.11.6) with ESMTP id hAIFnUl07553; Tue, 18 Nov 2003 10:49:30 -0500 (EST) Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30760) id <0HOK00G011AIN9@lmco.com>; Tue, 18 Nov 2003 10:49:30 -0500 (EST) Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF V6.1-1X6 #30760) with ESMTP id <0HOK00CAC1AHLI@lmco.com>; Tue, 18 Nov 2003 10:49:30 -0500 (EST) Received: from EMSS04M11.us.lmco.com ([144.219.10.27]) by EMSS04I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.2966); Tue, 18 Nov 2003 10:49:29 -0500 Date: Tue, 18 Nov 2003 15:50:00 -0000 From: "Newman, Mark (N-Superior Technical Resource Inc)" Subject: RE: async operation To: Daniel Jacobowitz , Mark Newman Cc: Andrew Cagney , gdb@sources.redhat.com Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-type: multipart/mixed; boundary="Boundary_(ID_2RfvsdUiKyDPYhUwudKApQ)" content-class: urn:content-classes:message X-MS-Has-Attach: yes X-MS-TNEF-Correlator: X-OriginalArrivalTime: 18 Nov 2003 15:49:29.0886 (UTC) FILETIME=[8D77BBE0:01C3ADEB] X-SW-Source: 2003-11/txt/msg00144.txt.bz2 This is a multi-part message in MIME format. --Boundary_(ID_2RfvsdUiKyDPYhUwudKApQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-length: 1962 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. However I am going to suspend asking what happened since my version of GDB has been modified to accept commands on a socket rather than directly from the keyboard by substituting the FD for the socket for stdin. I added (among other things) the following to main: gdb_stdout = marks_stdout; gdb_stderr = marks_stdout; dr_fd = fdopen(dr_in,"rw" ); instream = dr_fd; reinitialize_event_loop (); where dr_in is a socket. Among other things I had to add a reinit to the event loop to update rl_instream. These changes will not go into gdb before they are fully discussed on this forum. It may be my changes that are causing the problem. Mark Newman > -----Original Message----- > From: gdb-owner@sources.redhat.com > [mailto:gdb-owner@sources.redhat.com]On Behalf Of Daniel Jacobowitz > Sent: Tuesday, November 18, 2003 2:13 AM > To: Mark Newman > Cc: Andrew Cagney; Newman, Mark (N-Superior Technical Resource Inc); > gdb@sources.redhat.com > Subject: Re: async operation > > > On Mon, Nov 17, 2003 at 09:33:05PM -0800, Mark Newman wrote: > > I don't mean to sound dumb but could you clarify what > > "you can set a hook on `stop'" means? > > Search for hooks in the manual. > > > I see that and am working it now in conjunction with > > the interrupt command - unless the stop command(?) > > will do what I am looking for. GDBserver does not > > properly respond when in async and an "interrupt" is > > issued. > > What goes wrong? It should. Remember, async is an invention of the > client - the remote protocol is the same. > > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer > --Boundary_(ID_2RfvsdUiKyDPYhUwudKApQ) Content-type: text/plain; name=temp.txt Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=temp.txt Content-description: temp.txt Content-length: 2769 00000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff Sending packet: $m804953c,4#6d...Ack Packet received: 00200000 Sending packet: $mbffff81c,4#93...Ack Packet received: 0e000000 Sending packet: $mbffff818,4#68...Ack Packet received: 78563412 Sending packet: $mbffff7c0,50#c2...Ack Packet received: 0d0000004a6f686e20536d69746800429f6d0040b8240140426f6973652c20496461686f00a000407c280140882e014001000000000000001e5801420100000074f8ffbf7cf8ffbf1db2024234120000 remote_stop called Packet received: T0205:98f7ffbf;04:bcf5ffbf;08:61e50a42; Sending packet: $g#67...Ack Packet received: 1cf8ffbfb572fbb72f850408d0a21242b0f7ffbf28f8ffbf2020014074f8ffbff783040802020000230000002b0000002b0000002b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff 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) { Sending packet: $c#63...Ack remote_stop called Sending packet: $c#63...Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Sending packet: $c#63...Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Sending packet: $c#63...Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Sending packet: $c#63...Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it Packet instead of Ack, ignoring it --Boundary_(ID_2RfvsdUiKyDPYhUwudKApQ)--