From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16597 invoked by alias); 21 Aug 2008 20:11:58 -0000 Received: (qmail 16589 invoked by uid 22791); 21 Aug 2008 20:11:58 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Aug 2008 20:11:23 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m7LK64Mv023230; Thu, 21 Aug 2008 16:06:04 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m7LK64g5013334; Thu, 21 Aug 2008 16:06:04 -0400 Received: from opsy.redhat.com (vpn-10-87.bos.redhat.com [10.16.10.87]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m7LK63G7020664; Thu, 21 Aug 2008 16:06:03 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id A18E237828E; Thu, 21 Aug 2008 14:06:11 -0600 (MDT) To: Stan Shebs Cc: gdb@sourceware.org Subject: Re: Multiprocess GDB, formal spec References: <48A35D22.30705@codesourcery.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Fri, 22 Aug 2008 13:17:00 -0000 In-Reply-To: <48A35D22.30705@codesourcery.com> (Stan Shebs's message of "Wed\, 13 Aug 2008 15\:16\:02 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-08/txt/msg00246.txt.bz2 >>>>> "Stan" == Stan Shebs writes: Stan> set args ... Stan> set environment ... It occurred to me today that "set target-charset" will also have to be per-inferior. I am not sure if you were trying to make an exhaustive list here or not, but figured it was better to mention it than not. Note that this has some weird implications. Suppose you are debugging two running instances of "program", each with a different target charset. And suppose you set a breakpoint somewhere in that program, and that breakpoint's condition uses a string. Right now, gdb converts to the target charset early -- while parsing. However, in this case, you would actually want to do the conversion lazily. (Lazy would be better anyhow, since target-charset can be changed by the user at any time.) These are rather obscure scenarios. Tom