From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14341 invoked by alias); 24 Mar 2008 21:46:17 -0000 Received: (qmail 14332 invoked by uid 22791); 24 Mar 2008 21:46:16 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 24 Mar 2008 21:45:49 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 8B748983C6 for ; Mon, 24 Mar 2008 21:45:47 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 6D87C9810C for ; Mon, 24 Mar 2008 21:45:47 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JduUE-0004a7-NA for gdb@sourceware.org; Mon, 24 Mar 2008 17:45:46 -0400 Date: Mon, 24 Mar 2008 23:14:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: MI non-stop mode spec Message-ID: <20080324214546.GA17281@caradoc.them.org> Mail-Followup-To: gdb@sourceware.org References: <200803190016.02072.vladimir@codesourcery.com> <200803211211.18538.vladimir@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803211211.18538.vladimir@codesourcery.com> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes 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-03/txt/msg00210.txt.bz2 On Fri, Mar 21, 2008 at 12:11:17PM +0300, Vladimir Prus wrote: > It seems like I have over-engineered this one. The --global option > was meant so that we can evaluate expressions while the target is > running, but: > > - Generally, we cannot access target memory when all threads are > running > - GDB is full with assumptions that we have current thread and current > frame, so even if target can access memory when all threads is running, > gdb will still try to grab selected frame, and that will try to grab > target's register, and that will result in error. > > So, I'd like to remove the --global option. This means that the --thread > option must be used to specify which thread to operate on, and that > thread must be stopped. On targets that can access memory without stopping, I think that's a valuable feature that we ought to support if we can. Do you think adding --global is impractical? Maybe we can create a special frame for this - one which returns an error if you access its registers or unwind it, just a placeholder frame really. -- Daniel Jacobowitz CodeSourcery