From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3218 invoked by alias); 26 Apr 2008 18:16:36 -0000 Received: (qmail 3210 invoked by uid 22791); 26 Apr 2008 18:16:36 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 26 Apr 2008 18:16:18 +0000 Received: (qmail 7326 invoked from network); 26 Apr 2008 18:16:17 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 26 Apr 2008 18:16:17 -0000 From: Vladimir Prus To: gdb@sourceware.org Subject: [MI] enabling non-stop mode Date: Sat, 26 Apr 2008 22:19:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: Marc Khouzam MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804262216.16948.vladimir@codesourcery.com> 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: 2008-04/txt/msg00214.txt.bz2 Hello, I'm thinking about the best interface to query for, and enable non-stop mode when using MI. We presently have the -list-features command that list various things GDB supports. I've already proposed to add -enable-feature command to enable things that are off by default. Probably, we can extend this to enable feature that are not MI proper, say: (gdb) -list-features ^done,features=[....,"non-stop",....] (gdb) -enable-feature non-stop ^done The only issue here is that non-stop mode availability in general depends on the target, so maybe we should have a separate commands to list "target" feature and then enable target features? Thoughts? - Volodya