From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2256 invoked by alias); 2 Dec 2013 16:05:27 -0000 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 Received: (qmail 2241 invoked by uid 89); 2 Dec 2013 16:05:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 02 Dec 2013 16:05:25 +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 rB2G5GZr028918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 2 Dec 2013 11:05:16 -0500 Received: from barimba (ovpn-113-124.phx2.redhat.com [10.3.113.124]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id rB2G5ElC031654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Dec 2013 11:05:15 -0500 From: Tom Tromey To: Hui Zhu Cc: gdb-patches ml Subject: Re: [PATCH] Make "backtrace" doesn't print python stack if init python dir get fail References: <52974146.70805@mentor.com> Date: Mon, 02 Dec 2013 16:05:00 -0000 In-Reply-To: <52974146.70805@mentor.com> (Hui Zhu's message of "Thu, 28 Nov 2013 21:12:38 +0800") Message-ID: <8761r7w85h.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-12/txt/msg00040.txt.bz2 >>>>> "Hui" == Hui Zhu writes: Hui> So if init python dir get fail, "backtrace" will print python Hui> stack. But GDB already output error when it start. I make a patch Hui> let it doesn't print python stack if init python dir get fail. Perhaps instead the setting of gdb_python_initialized should be moved to finish_python_initialization. Tom