From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5934 invoked by alias); 13 Apr 2012 13:07:56 -0000 Received: (qmail 5926 invoked by uid 22791); 13 Apr 2012 13:07:55 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,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, 13 Apr 2012 13:07:39 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q3DD7d0I031647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 13 Apr 2012 09:07:39 -0400 Received: from host2.jankratochvil.net (ovpn-116-70.ams2.redhat.com [10.36.116.70]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q3DD7ZYI028096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 13 Apr 2012 09:07:38 -0400 Date: Fri, 13 Apr 2012 13:07:00 -0000 From: Jan Kratochvil To: Folkert van Heusden Cc: gdb@sourceware.org Subject: Re: gdb and threads Message-ID: <20120413130734.GA22952@host2.jankratochvil.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes 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: 2012-04/txt/msg00096.txt.bz2 On Thu, 12 Apr 2012 11:44:26 +0200, Folkert van Heusden wrote: > Now when my program gets a SIGSEGV, I can use 'bt' in gdb to get a backtrace. > Can I be sure that the backtrace I get is the one from the thread > causing the SIGSEGV? Assuming GDB default mode, not async/non-stop modes. With live process yes. But be aware multiple threads may segfault "at once". With core files it depends which thread is put first in the core file, with Linux kernel in practice it works, I do not know guarantees of it in Linux kernel. Regards, Jan