Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vadim Shmelev <vadim.shmelev@acronis.com>
Cc: 'Michael Snyder' <Michael.Snyder@access-company.com>,
		gdb@sourceware.org
Subject: Re: GDB receives SIGKILL
Date: Tue, 03 Apr 2007 14:37:00 -0000	[thread overview]
Message-ID: <20070403143738.GA4919@caradoc.them.org> (raw)
In-Reply-To: <200704030712.l337CrhN031558@imap.acronis.ru>

On Tue, Apr 03, 2007 at 11:15:59AM +0400, Vadim Shmelev wrote:
> -COMMENT-------------------------------------------------------------
> If I enable SIG32 and SIG33 gdb will be stopped at every thread switch.
> -END COMMENT---------------------------------------------------------

Figure out why.  If this is happening, GDB thread support is not
working, and you can not expect anything to behave properly.

> I forget -- do we have linuxthreads debugging working with static link?
> [question for the other maintainers]
> 
> -COMMENT---------------------------------------------------------------
> I'm also interested very much in answer.
> -END COMMENT-----------------------------------------------------------

Sometimes yes, sometimes no.  Usually no.  There are patches for this
problem in the glibc bugzilla that have still not been applied.

> > Reading symbols from shared object read from target memory...done.
> > Loaded system supplied DSO at 0xffffe000
> 
> What's this?  System supplied DSO?

It's the vDSO.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-04-03 14:37 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 [this message]
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=20070403143738.GA4919@caradoc.them.org \
    --to=drow@false.org \
    --cc=Michael.Snyder@access-company.com \
    --cc=gdb@sourceware.org \
    --cc=vadim.shmelev@acronis.com \
    /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