From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24304 invoked by alias); 24 Jul 2002 18:52:44 -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 24293 invoked from network); 24 Jul 2002 18:52:43 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 24 Jul 2002 18:52:43 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 19A903DBF; Wed, 24 Jul 2002 14:52:43 -0400 (EDT) Message-ID: <3D3EF77A.7020304@ges.redhat.com> Date: Wed, 24 Jul 2002 11:52:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020708 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Kegel Cc: Daniel Jacobowitz , Lucy Zhang , gdb@sources.redhat.com Subject: Re: Thread signal information References: <004501ea8fb2$e33da4c0$9a0a0109@zhangl> <20020724160422.GA5346@nevyn.them.org> <3D3EE3D4.9030502@ixiacom.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg00254.txt.bz2 > Does one give up anything by doing a postmortem gdb session > rather than a live session? Obviously one loses the ability to continue, > but what else? Presumably (once we coax the OS into producing the > proper core dump) we still can do 'info threads' and 'backtrace' on > each thread, right? Main thing you loose is inferior function calls. Often they are useful when it comes to displaying data. Andrew