From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16528 invoked by alias); 23 Dec 2003 15:02:16 -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 16517 invoked from network); 23 Dec 2003 15:02:15 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 23 Dec 2003 15:02:15 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AYo32-0005Xc-Dh; Tue, 23 Dec 2003 10:02:12 -0500 Date: Tue, 23 Dec 2003 15:02:00 -0000 From: Daniel Jacobowitz To: srikrish Cc: gdb@sources.redhat.com Subject: Re: gdb stack trace shows only those frames after the signal Message-ID: <20031223150212.GB21228@nevyn.them.org> Mail-Followup-To: srikrish , gdb@sources.redhat.com References: <00c701c3c965$424c6a90$fd0eb609@srikrishnan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00c701c3c965$424c6a90$fd0eb609@srikrishnan> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-12/txt/msg00257.txt.bz2 Please fix your line wrapping if you expect anyone to read your e-mail. This is a known problem on recent systems; search the archives for information about the vsyscall DSO. At least I believe that will show up in signal backtraces also. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer