From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29752 invoked by alias); 15 Sep 2004 17:36:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29739 invoked from network); 15 Sep 2004 17:36:54 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 15 Sep 2004 17:36:54 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8FHadux028938 for ; Wed, 15 Sep 2004 13:36:44 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8FHaXr00419; Wed, 15 Sep 2004 13:36:33 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D34D528D2; Wed, 15 Sep 2004 13:34:21 -0400 (EDT) Message-ID: <41487D1D.7040504@gnu.org> Date: Wed, 15 Sep 2004 17:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040831 MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Abort backtrace when consecutive zero PCs? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00121.txt.bz2 Hello, One backtrace infinite loop case I've noticed (especially on ia64) is where successive frames all have a zero PC. While we definitly need to allow a backtrace through a single zero PC (for a NULL pointer call - signull.exp) should we make GDB abort when two or more consecutive frames have a zero PC? (mumble something about a runtime option) thoughts? Andrew