From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9942 invoked by alias); 24 Mar 2009 14:28:46 -0000 Received: (qmail 9306 invoked by uid 22791); 24 Mar 2009 14:28:42 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from wf-out-1314.google.com (HELO wf-out-1314.google.com) (209.85.200.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Mar 2009 14:28:35 +0000 Received: by wf-out-1314.google.com with SMTP id 23so3142031wfg.24 for ; Tue, 24 Mar 2009 07:28:33 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 24 Mar 2009 14:28:00 -0000 Received: by 10.143.3.7 with SMTP id f7mr3421366wfi.92.1237904913296; Tue, 24 Mar 2009 07:28:33 -0700 (PDT) Message-ID: <8c675e9b0903240728i7e044580yae1deff480b3ffc9@mail.gmail.com> Subject: GDB bt command and core dumps From: Amol Lad To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2009-03/txt/msg00139.txt.bz2 Hi, I'm working on an ARM9 platform (running Linux 2.6.18) and using gdb 6.6 compiled for the platform. My application is a multithreaded application and on a crash it generates core of around 200MByte. I'm looking to reduce the size of the core file and I _only_ need gdb 'bt' command output ; no other debugging information (i.e I'm only interested in the call trace) - I tried ulimit -c command but the core produced are not useful in most cases - I changed kernels fs/binfmt_elf.c file and modified maydump function to just add crashed thread's stack in the core but no success What all information should be present in the core file so that bt output works reliably. Is stack of crashed thread not enough ? My application is compiled with -O2 (hence -fomit-frame-pointer) Thanks -- Amol Sent from: Bangalore KA India.