From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25484 invoked by alias); 22 Sep 2003 20:46:26 -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 25464 invoked from network); 22 Sep 2003 20:46:25 -0000 Received: from unknown (HELO vortex.servnow.com) (64.5.48.88) by sources.redhat.com with SMTP; 22 Sep 2003 20:46:25 -0000 Received: from adsl-63-205-138-219.dsl.lsan03.pacbell.net ([63.205.138.219] helo=tbird) by vortex.servnow.com with asmtp (Exim 4.20) id 1A1XZk-0000Wh-HA for gdb@sources.redhat.com; Mon, 22 Sep 2003 16:46:28 -0400 Message-ID: <0ca201c3814a$8e899490$0200a8c0@tbird> From: "Robin Rowe" To: Subject: Crash log Date: Mon, 22 Sep 2003 20:46:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vortex.servnow.com X-AntiAbuse: Original Domain - sources.redhat.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - movieeditor.com X-SW-Source: 2003-09/txt/msg00278.txt.bz2 Hi. This isn't really a gdb question, but I don't know where else to ask. When a program catches a bad signal such as SIGSEGV I want to write a crash log entry before the program exits. Is there anything useful I can put in the log besides the name of the program and when it crashed? Is it ok to write this log from my signal catcher, or should it first fork? Is there some kind of useful state info (assuming the program contains no debugging info) that I can write to a log file at the time of death? Can I get an instruction pointer that I can relate back to the original souce somehow to determine what line of code crashed? Thanks! Robin --------------------------------------------------------------------------- Robin.Rowe@MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software