From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31662 invoked by alias); 4 May 2008 17:03:26 -0000 Received: (qmail 31633 invoked by uid 22791); 4 May 2008 17:03:23 -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; Sun, 04 May 2008 17:03:05 +0000 Received: (qmail 18901 invoked from network); 4 May 2008 17:03:03 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 4 May 2008 17:03:03 -0000 From: Vladimir Prus To: gdb@sourceware.org Subject: Reporting non-stop support Date: Sun, 04 May 2008 17:03:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805042102.30612.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-05/txt/msg00040.txt.bz2 As discussed before, it would be nice if GDB could report if the current target supports non-stop, so that frontend can act accordingly (even if "accordingly" means saying "sorry, non-stop is not supported"). However, it's a bit tricky, because until we do "run", the two targets on the target stack are dummy target and exec_ops -- neither of which, naturally, have any clue about non-stop. It's only when we do "run" when find_default_run_target is called, and something reasonable is pushed to the target stack. Which means that until we do "run", we don't know if the target supports non-stop, and when we do "run", it's a bit too later to set non-stop mode. Any suggestions? - Volodya