public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'anticompetitive illegal monopoly'" <cygwin-talk@cygwin.com>
Subject: RE: Bring me the head of Bill Gates!
Date: Wed, 24 Sep 2008 22:03:00 -0000	[thread overview]
Message-ID: <01c201c91e91$37d3fa20$9601a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20080923143817.GB6284@ednor.casa.cgf.cx>

Christopher Faylor wrote on 23 September 2008 15:38:

> On Tue, Sep 23, 2008 at 04:57:57PM +1000, Gareth Pearce wrote:
>> price of bread?
> 
> Yeah, I'm missing the context here as well.
> 
> cgf

 <koff> been away with lurgy.

  Anyway.  The point was..

> Gareth Pearce wrote on 23 September 2008 07:58:
> 
>> Umm, the alternate functions are listed in the topic ... as TlsGetValue
>> and CoGetContextToken ...

  Those two functions only give you access to the tiniest fraction of the
stuff that is now hidden behind the nondescript

>>>   BYTE Reserved1[1952];

  Remember [fs:4] = stack bottom = tls area?  That's gone now.  Can't access
the exception registration chain at [fs:0] either.  All that useful stuff -
last error value, peb pointer, environment - it's all out of bounds now.
Can't look at it in the TEB.  Can't get it via the NT api info funcs that
might otherwise have provided another route to the data, because they've been
retired too.  And there's no equivalent win32 func for most of it either -
none of the GetThreadXxxxx functions are any help there.

  So.  How's anyone except MS supposed to write C runtimes, compilers and
support libraries, or posix emulation layers now?

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

      reply	other threads:[~2008-09-24 22:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 22:06 Dave Korn
2008-09-23  6:58 ` Gareth Pearce
2008-09-23 14:38   ` Christopher Faylor
2008-09-24 22:03     ` Dave Korn [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='01c201c91e91$37d3fa20$9601a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=cygwin-talk@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).