From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23192 invoked by alias); 23 Jun 2008 16:32:16 -0000 Received: (qmail 23180 invoked by uid 22791); 23 Jun 2008 16:32:16 -0000 X-Spam-Check-By: sourceware.org Received: from f132.mail.ru (HELO f132.mail.ru) (194.67.57.113) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 23 Jun 2008 16:31:56 +0000 Received: from mail by f132.mail.ru with local id 1KAoxN-0001HF-00 for gdb@sourceware.org; Mon, 23 Jun 2008 20:31:53 +0400 Received: from [212.92.145.7] by win.mail.ru with HTTP; Mon, 23 Jun 2008 20:31:53 +0400 From: Dmitry Smirnov To: gdb@sourceware.org Subject: How to catch GDB crash Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 Date: Mon, 23 Jun 2008 16:32:00 -0000 Reply-To: Dmitry Smirnov Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Spam: Not detected 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: 2008-06/txt/msg00217.txt.bz2 Hi, I've encountered the very annoying problem with GDB. While debugging, it crashes for some reason and I cannot catch this moment. I have a possibility to attach to the running process with another GDB, but it does not help. Perhaps, there is some way to catch some system exception or something similar? I'm using a litle bit complex setup, so there is no much freedom (at least I cannot simplify the situation). First, I'm debugging from Eclipse (and it looks this crash happens only while running from Eclipse, I've tried from commad line - there is no crash). The debugger I'm using is cross-compiled arm-elf-gdb. It is compiled on windows (i686) platform: GNU gdb (GDB) 6.8.50.20080620 ... This GDB was configured as "--host=i686-pc-cygwin --target=arm-elf". I doubt this can be linked to GDB version. I recall I've seen this crash earlier with arm-elf-gdb 6.5 from GNUARM. I was just skipped this crash somehow but now I cannot continue my job. This arm-elf-gdb is running against skyeye simulator as a remote target. As you can see there are many possibilities for mailfunctioning software (Eclipse, GDB, skyeye). But the only way I can find the root cause is to debug the crash in arm-elf-gdb. While crashing it attempts to create the crashdump file, but it is incomplete and Cygwin gdb cannot recognize it. Typically it contains just three lines: Stack trace: Frame Function Args 0022E268 7C802532 (00000058 If attached, Cygwin GDB just reporting me: Program exited with code 037777777777. Is there any way to stop arm-elf-gdb on some critical error? Dmitry