From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1099 invoked by alias); 2 Apr 2007 10:01:18 -0000 Received: (qmail 1080 invoked by uid 22791); 2 Apr 2007 10:01:16 -0000 X-Spam-Check-By: sourceware.org Received: from kz-easy.com (HELO almaty.kz-easy.com) (85.214.25.173) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 02 Apr 2007 11:01:10 +0100 Received: from alatau.radix50.net (dslb-088-064-009-126.pools.arcor-ip.net [88.64.9.126]) (authenticated bits=0) by almaty.kz-easy.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l32A12pr030888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 2 Apr 2007 12:01:03 +0200 Received: from alatau.radix50.net (localhost [127.0.0.1]) by alatau.radix50.net (8.13.8/8.13.8/Debian-2) with ESMTP id l32A0pqQ025300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 2 Apr 2007 12:00:52 +0200 Received: (from ibr@localhost) by alatau.radix50.net (8.13.8/8.13.8/Submit) id l32A0pdU025299 for gdb@sourceware.org; Mon, 2 Apr 2007 12:00:51 +0200 Date: Mon, 02 Apr 2007 10:01:00 -0000 From: Baurzhan Ismagulov To: gdb@sourceware.org Subject: Re: GDB receives SIGKILL Message-ID: <20070402100051.GA19126@radix50.net> Mail-Followup-To: gdb@sourceware.org References: <200704020753.l327rr5p027400@imap.acronis.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200704020753.l327rr5p027400@imap.acronis.ru> User-Agent: Mutt/1.5.13 (2006-08-11) 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: 2007-04/txt/msg00007.txt.bz2 Hello Vadim, On Mon, Apr 02, 2007 at 11:57:01AM +0400, Vadim Shmelev wrote: > I'm novice in Linux and during of application debugging that linked > statically I bump into the following problem: debugger receives SIGKILL and > exits. Are you using a front-end before gdb? If yes, you could strace it to see whether it kills gdb. If not, check the kernel logs for the OOM killer. With kind regards, -- Baurzhan Ismagulov http://www.kz-easy.com/