From: "Vadim Shmelev" <vadim.shmelev@acronis.com>
To: "'Baurzhan Ismagulov'" <ibr@radix50.net>
Cc: <gdb@sourceware.org>
Subject: RE: GDB receives SIGKILL
Date: Mon, 02 Apr 2007 13:44:00 -0000 [thread overview]
Message-ID: <200704021344.l32DiWiT016756@imap.acronis.ru> (raw)
In-Reply-To: <20070402100051.GA19126@radix50.net>
Thanks for response, Baurzhan. I will try to describe the problem in
details. Application works satisfactorily, but some results are unexpected.
Strace works normally too. Problem occurs during debug process only. RAM is
2 Gb and there is no out of memory messages in log. There is output from gdb
session:
GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-asplinux-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".
(gdb) handle SIG32 nostop noprint
Signal Stop Print Pass to program Description
SIG32 No No Yes Real-time event 32
(gdb) handle SIG33 nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) b
'ComputerManagement::CreateLocalLinuxHardwareInfo(Fomatik::Computer*)'
Breakpoint 1 at 0x9053fe6: file ../../../include/processor/ref/allocator.h,
line 23.
(gdb) r
Starting program: /mnt/afc_agent.exe
warning: shared library handler failed to enable breakpoint
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xffffe000
Detaching after fork from child process 2322.
Detaching after fork from child process 2325.
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
Current language: auto; currently c++
The next output string looks strange ' warning: shared library handler
failed to enable breakpoint' as application is linked statically. Any
advises?
With best regards, Vadim
-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf
Of Baurzhan Ismagulov
Sent: Monday, April 02, 2007 2:01 PM
To: gdb@sourceware.org
Subject: Re: GDB receives SIGKILL
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/
next prev parent reply other threads:[~2007-04-02 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 7:54 Vadim Shmelev
2007-04-02 10:01 ` Baurzhan Ismagulov
2007-04-02 13:44 ` Vadim Shmelev [this message]
2007-04-02 17:54 ` Michael Snyder
2007-04-03 7:13 ` Vadim Shmelev
2007-04-03 14:37 ` Daniel Jacobowitz
2007-04-03 19:47 ` Michael Snyder
2007-04-04 12:47 ` Vadim Shmelev
2007-04-04 18:20 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704021344.l32DiWiT016756@imap.acronis.ru \
--to=vadim.shmelev@acronis.com \
--cc=gdb@sourceware.org \
--cc=ibr@radix50.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox