From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>,
Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: Re: Add base linux native multi-process support.
Date: Mon, 18 May 2009 02:30:00 -0000 [thread overview]
Message-ID: <200905180330.38896.pedro@codesourcery.com> (raw)
In-Reply-To: <200905180327.00969.pedro@codesourcery.com>
Sigh, EMISSINGWORD:
On Monday 18 May 2009 03:27:00, Pedro Alves wrote:
> the testsuite, so I think it's about good to go. The only piece
> of linux-thread-db.c that isn't per-inferior yet is LinuxThreads',
^ signals
this ...
/* Non-zero if we have determined the signals used by the threads
library. */
static int thread_signals;
static sigset_t thread_stop_set;
static sigset_t thread_print_set;
--
Pedro Alves
next prev parent reply other threads:[~2009-05-18 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 19:55 Pedro Alves
2009-04-16 19:15 ` Tom Tromey
2009-04-20 18:06 ` Pedro Alves
2009-04-20 18:29 ` Tom Tromey
2009-05-18 2:26 ` Pedro Alves
2009-05-18 2:30 ` Pedro Alves [this message]
2009-05-18 13:45 ` Pedro Alves
2009-05-18 14:10 ` Pedro Alves
2009-05-18 17:10 ` Paul Pluzhnikov
2009-05-18 17:31 ` Pedro Alves
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=200905180330.38896.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=tromey@redhat.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