From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10975 invoked by alias); 6 Dec 2011 15:40:42 -0000 Received: (qmail 10961 invoked by uid 22791); 6 Dec 2011 15:40:40 -0000 X-SWARE-Spam-Status: No, hits=-7.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_SM 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; Tue, 06 Dec 2011 15:40:27 +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 pB6FeQCQ000650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Dec 2011 10:40:26 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id pB6FeQ1X025378; Tue, 6 Dec 2011 10:40:26 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pB6FeOMk022885; Tue, 6 Dec 2011 10:40:25 -0500 From: Tom Tromey To: asmwarrior Cc: gdb-patches@sourceware.org Subject: Re: [patch] avoid the crash of gdb+pretty printer on initialized local variables References: <4ED379D8.4060808@gmail.com> <4ED8534D.2050100@gmail.com> <4EDAD0B3.80505@gmail.com> <4EDDAD62.9000103@gmail.com> Date: Tue, 06 Dec 2011 15:41:00 -0000 In-Reply-To: <4EDDAD62.9000103@gmail.com> (asmwarrior@gmail.com's message of "Tue, 06 Dec 2011 13:51:30 +0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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-12/txt/msg00174.txt.bz2 >>>>> ">" == ext asmwarrior writes: >> I forget to mention that My gdb was build with -O0 and -g, so I think >> no optimization was used in building gdb. >> The problem is that gdb still crash when it try to pretty-print the >> uninitialized local variables. I think the best thing to do is find out why that happens, and fix the root cause. gdb should not crash. Tom