From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19578 invoked by alias); 1 Jul 2011 14:14:22 -0000 Received: (qmail 19570 invoked by uid 22791); 1 Jul 2011 14:14:21 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 Jul 2011 14:14:02 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p61EDwrK032368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 1 Jul 2011 10:13:58 -0400 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p61EDuF5024363; Fri, 1 Jul 2011 10:13:57 -0400 From: Phil Muldoon To: Taisuke Yamada Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] sys.argv and ipython (interactive python) support in GDB/Python References: Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Fri, 01 Jul 2011 14:14:00 -0000 In-Reply-To: (Taisuke Yamada's message of "Fri, 1 Jul 2011 23:10:02 +0900") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-07/txt/msg00013.txt.bz2 Taisuke Yamada writes: > Not really. I'm just setting "gdb" as a text label to use when generating > log message both in python and python library. Just like in C, it *usually* > points to executing script itself, but after all, there's nothing that > gurantees that. > > Alternatively, you can do "PySys_SetArgvEx (0, NULL, 0);", but then > python will automatically generate empty (= "") argv[0]. That means any > logs generated will be somewhat odd, so my idea was to have something > instead. Ah ok, thanks for the explanation. > If you're concerned, maybe "python-gdb" would be better. I'm not, your explanation is good. Cheers Phil