From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12795 invoked by alias); 6 Aug 2010 18:39:20 -0000 Received: (qmail 12780 invoked by uid 22791); 6 Aug 2010 18:39:19 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_20 X-Spam-Check-By: sourceware.org Received: from etinternational-gw.customer.alter.net (HELO etinternational.com) (63.125.108.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 06 Aug 2010 18:39:15 +0000 Received: from [192.168.9.69] (random.xmen.eti [192.168.9.69]) (Authenticated sender: bheilig) by etinternational.com (Postfix) with ESMTPSA id 9C538F00D5 for ; Fri, 6 Aug 2010 14:39:13 -0400 (EDT) Subject: Problems with non-stop - Porting gdb to Cyclops64 From: Brian Heilig To: gdb In-Reply-To: <201008051519.39349.pedro@codesourcery.com> References: <1280510022.1560.20.camel@random> <201008021435.16106.pedro@codesourcery.com> <1281016608.1560.79.camel@random> <201008051519.39349.pedro@codesourcery.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 06 Aug 2010 18:39:00 -0000 Message-ID: <1281119953.1560.96.camel@random> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-08/txt/msg00042.txt.bz2 Dear list, I am having trouble making gdb happy in non-stop mode. When I connect to my target in non-stop mode gdb queries for the list of active threads. It then sends a stop request for the first thread in the list, "vCont;t:1". The documentation for this feature states: "A stop reply should be generated for any affected thread not already stopped. When a thread is stopped by means of a `t' action, the corresponding stop reply should indicate that the thread has stopped with signal `0', regardless of whether the target uses some other signal as an implementation detail." So I send back my stop response: "$T00;thread:1;". gdb responds with "Stopping Thread 1 failed: T00;thread:1;" and disconnects from the target. I tried this same test on my Linux desktop using version 7.1-ubuntu and received a very different response. Server: gdbserver :0 a.out Client: gdb a.out Set non-stop on the client and then connect with "target remote :". Client sends "vCont;t:" Server responds with "$OK". The gdb prompt never appears and (as far as I can tell) nothing can be done with the gdb session. Am I doing something wrong? Thanks, Brian