From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7007 invoked by alias); 8 Jul 2011 20:22:24 -0000 Received: (qmail 6997 invoked by uid 22791); 8 Jul 2011 20:22:23 -0000 X-SWARE-Spam-Status: No, hits=-6.1 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, 08 Jul 2011 20:22:09 +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 p68KM9pY006052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 8 Jul 2011 16:22:09 -0400 Received: from fche.csb (vpn-224-66.phx2.redhat.com [10.3.224.66]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p68KM9eC032057; Fri, 8 Jul 2011 16:22:09 -0400 Received: by fche.csb (Postfix, from userid 2569) id 44A735813A; Fri, 8 Jul 2011 16:22:08 -0400 (EDT) To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: FYI: put a QUIT in DWARF expression evaluator References: From: fche@redhat.com (Frank Ch. Eigler) Date: Sat, 09 Jul 2011 06:40:00 -0000 In-Reply-To: (Tom Tromey's message of "Fri, 08 Jul 2011 10:02:40 -0600") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00260.txt.bz2 tromey wrote: > Today I wondered what would happen if I modified pr10770.c to fail, > causing an infinite loop while evaluating a DWARF expression. The > answer is that gdb hangs and I had to kill it from the shell. > [...] > FWIW, as far as I know, no such DWARF has ever been found in the wild. But perhaps other non-interactive services that rely on gdb to do backtraces (pstack?) could be tricked into looping indefinitely. To what extent is gdb vulnerable to specially crafted target memory state causing indefinitely-long processing? - FChE