From: Daniel Jacobowitz <dan@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, "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: Thu, 28 Jan 2010 17:01:00 -0000 [thread overview]
Message-ID: <20100128170103.GA9936@caradoc.them.org> (raw)
In-Reply-To: <20100127221236.GA4746@host0.dyn.jankratochvil.net>
On Wed, Jan 27, 2010 at 11:12:36PM +0100, Jan Kratochvil wrote:
> No regressions on {x86_64,x86_64-m32,i686}-fedora12-linux-gnu and on
> x86_64-fedora12-linux-gnu via gdbserver.
>
> Verified linux_supports_tracefork_flag gets still set with the patch.
>
> Verified unsetting HAVE_FORK for gdb/gdbserver/ still works the same.
>
> gdb/ already tests HAVE_FORK in config.in but it is brought in by other
> macros, therefore rather added an explicit configure.ac test for it.
>
> Have not found an easy enough uClinux disk image of some arch for qemu-*.
I don't recommend testing HAVE_FORK; uClibc may provide a dummy fork
that returns ENOSYS. There's a HAS_NOMMU in linux-low.c that should work.
For the test case, what defines UCLINUX?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-01-28 17:01 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 [this message]
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
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=20100128170103.GA9936@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jan.kratochvil@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