From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2686 invoked by alias); 12 May 2003 21:48:17 -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 2581 invoked from network); 12 May 2003 21:48:16 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sources.redhat.com with SMTP; 12 May 2003 21:48:16 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3p2/8.9.3) with ESMTP id RAA20757 for ; Mon, 12 May 2003 17:44:58 -0400 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id RAA31246 for ; Mon, 12 May 2003 17:48:15 -0400 Message-ID: <17d101c318d0$3107ba00$0202040a@catdog> From: "Kris Warkentin" To: "Gdb@Sources.Redhat.Com" Subject: How to indicate failing thread in core file. Date: Mon, 12 May 2003 21:48:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-05/txt/msg00214.txt.bz2 I'm fixing up our core-file reading stuff in elf.c and trying to see how to indicate the thread that failed. I'm only setting the core_signal and core_lwpid on the thread that got the signal but that doesn't seem to be doing the trick. How does gdb know which thread was currently running when the core was generated? cheers, Kris