From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14111 invoked by alias); 13 Oct 2009 13:47:01 -0000 Received: (qmail 14098 invoked by uid 22791); 13 Oct 2009 13:46:59 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_20,SPF_PASS X-Spam-Check-By: sourceware.org Received: from dlpdemo.checkpoint.com (HELO dlpdemo.checkpoint.com) (194.29.32.54) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Oct 2009 13:46:53 +0000 X-CheckPoint: {4AD482DF-2-14201DC2-FFFF} Received: by dlpdemo.checkpoint.com (Postfix, from userid 105) id 0E8F729C00C; Tue, 13 Oct 2009 15:46:50 +0200 (IST) Received: from michael.checkpoint.com (michael.checkpoint.com [194.29.32.68]) by dlpdemo.checkpoint.com (Postfix) with ESMTP id E88FF29C002 for ; Tue, 13 Oct 2009 15:46:49 +0200 (IST) X-CheckPoint: {4AD482DF-0-14201DC2-FFFF} Received: from il-ex01.ad.checkpoint.com (localhost [127.0.0.1]) by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id n9DDknhu001705 for ; Tue, 13 Oct 2009 15:46:49 +0200 (IST) Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Tue, 13 Oct 2009 15:46:51 +0200 From: Avi Gozlan To: "gdb@sourceware.org" CC: Avi Gozlan Date: Tue, 13 Oct 2009 13:47:00 -0000 Subject: Core file shows stack correctly with GDB 5.3.9 but not with GDB 6.8 Message-ID: <9C4E85B61203CD419BB3A638E5F68333010FB207482F@il-ex01.ad.checkpoint.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-10/txt/msg00236.txt.bz2 Hello, Usually, when we open core files using GDB 6.8 the stack shows correctly (w= hile GDB 5.3.9 shows '?? ()' for several frames). However, from time to time we encounter core files for which the opposite i= s correct. Namely, we can see the stack correctly with 5.3.9 but not with 6= .8. This phenomenon happens on the same machine and executables are compiled us= ing the same environment. We have no idea regarding the cause of this weird= behavior.=20 I would be thankful if you could shed some light on this issue. Regards, Avi Email secured by Check Point Email secured by Check Point