From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: gdb-patches@sourceware.org, Andreas Schwab <schwab@redhat.com>
Subject: Re: [PATCH, M68K] Handle TLS
Date: Wed, 19 May 2010 15:06:00 -0000 [thread overview]
Message-ID: <4BF3F2A3.2040607@codesourcery.com> (raw)
In-Reply-To: <4AF13ABF.7030407@codesourcery.com>
On 11/4/09 11:26 AM, Maxim Kuvyrkov wrote:
> Daniel Jacobowitz wrote:
>> On Tue, Nov 03, 2009 at 07:12:09PM +0300, Maxim Kuvyrkov wrote:
>>> Hi,
>>>
>>> The following simple patch adds handling of TLS to m68k gdbserver.
>>>
>>> A corresponding kernel patch is being reviewed here
>>> <http://marc.info/?l=linux-m68k&m=125447760017098&w=2>.
>>>
>>> Tested on coldfire-linux.
>>>
>>> OK to apply?
>>
>> This is fine with two caveats:
>>
>> * I think it would be best to not apply it until you have an ack for
>> the kernel patch defining PTRACE_GET_THREAD_AREA.
>
> OK, that may take a while though.
>>
>> * Provide a fallback definition for PTRACE_GET_THREAD_AREA. I assume
>> existing m68k kernel headers do not define it, so the build would
>> fail.
>
> OK.
The kernel patches implementing NPTL support and PTRACE_GET_THREAD_AREA
were checked in several months ago.
I have now checked this GDB patch with definition of ps_get_thread_area
conditioned on "#ifdef PTRACE_GET_THREAD_AREA".
Regards,
--
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724
prev parent reply other threads:[~2010-05-19 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 16:12 Maxim Kuvyrkov
2009-11-03 23:08 ` Daniel Jacobowitz
2009-11-04 8:26 ` Maxim Kuvyrkov
2010-05-19 15:06 ` Maxim Kuvyrkov [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=4BF3F2A3.2040607@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@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