Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: "H.J. Lu" <hjl.tools@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: [patch] Fix CLONE_VM vs. TLS  [Re: Is CLONE_VM really needed in     gdbserver?]
Date: Mon, 01 Feb 2010 20:20:00 -0000	[thread overview]
Message-ID: <20100201202010.GA9900@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100129124128.GA6588@host0.dyn.jankratochvil.net>

On Fri, 29 Jan 2010 13:41:28 +0100, Jan Kratochvil wrote:
> Going to check it in in some times as this change is IMO pre-approved.
[...]
> gdb/gdbserver/
> 2010-01-29  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	PR libc/11214:
> 	* linux-low.c (linux_tracefork_child) [!(__UCLIBC__ && HAS_NOMMU)]: New.
> 	(linux_test_for_tracefork): Move `stack' into [__UCLIBC__ && HAS_NOMMU].
> 	(linux_test_for_tracefork) [!(__UCLIBC__ && HAS_NOMMU)]: New.
> 
> gdb/testsuite/
> 2010-01-29  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	PR libc/11214:
> 	* gdb.threads/current-lwp-dead.c: Include features.h.
> 	(HAS_NOMMU): New.
> 	(fn, main): Move CLONE_VM into [__UCLIBC__ && HAS_NOMMU].

Checked-in:
	http://sourceware.org/ml/gdb-cvs/2010-02/msg00010.html


Regards,
Jan


      reply	other threads:[~2010-02-01 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6dc9ffc81001261551j6221db6v88e96713d6dd9497@mail.gmail.com>
     [not found] ` <20100127000821.GA29862@caradoc.them.org>
2010-01-27 22:12   ` Jan Kratochvil
2010-01-28 16:22     ` H.J. Lu
2010-01-28 17:01     ` Daniel Jacobowitz
2010-01-29  1:26       ` Jan Kratochvil
2010-01-29  2:30         ` Daniel Jacobowitz
2010-01-29 12:41           ` Jan Kratochvil
2010-02-01 20:20             ` Jan Kratochvil [this message]

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=20100201202010.GA9900@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.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