From: "Vadim Shmelev" <vadim.shmelev@acronis.com>
To: "'Michael Snyder'" <Michael.Snyder@access-company.com>
Cc: <gdb@sourceware.org>
Subject: RE: GDB receives SIGKILL
Date: Wed, 04 Apr 2007 12:47:00 -0000 [thread overview]
Message-ID: <200704041247.l34ClW9n030152@imap.acronis.ru> (raw)
In-Reply-To: <1175629645.11945.11.camel@svmsnyderlnx.palmsource.com>
Thanks for comments, Daniel and Michael. I will try to describe my
environment.
For statically building of application I use gcc 4.1.1, glibc 2.3.2 and all
glibc components configured and built together. NPTL threads are not used.
Target platform is VMware ESX Server with 2.4.21 kernel, accordingly dynamic
linking doesn't match, as glibc's conflict is possible. How I can realize,
that problem doesn't have decision, but I should know possible reasons for
receiving SIG32 and SIG33 signals.
Best regards, Vadim
next prev parent reply other threads:[~2007-04-04 12:47 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
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 [this message]
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=200704041247.l34ClW9n030152@imap.acronis.ru \
--to=vadim.shmelev@acronis.com \
--cc=Michael.Snyder@access-company.com \
--cc=gdb@sourceware.org \
/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