From: "Teemu Nätkinniemi" <tnatkinn@gmail.com>
To: cygwin-patches@cygwin.com
Subject: Re: Add support for Windows 8, first step
Date: Wed, 12 Oct 2011 20:45:00 -0000 [thread overview]
Message-ID: <4E95FC38.1090500@gmail.com> (raw)
In-Reply-To: <20111012082643.GA10913@calimero.vinschen.de>
Hello Corinna,
On 12.10.2011 11:26, Corinna Vinschen wrote:
> First of all, we need a copyright assignment from you before we can
> accept non-trivial patches to Cygwin, see http://cygwin.com/contrib.html,
> the "Before you get started" section.
I am going to do that just in case I actually get something working (see
below).
> Windows 8 will very likely support the FAST_CWD stuff, the problem is
> just to find out how to find the global pointer pointing to the current
> FAST_CWD structure, and then, if the FAST_CWD structure changed.
It does do that, the code looks almost the same as in Windows 7. There
are some differences that I haven't figured out yet. But I might
actually wait for a beta version of Windows 8 before going forward.
> Therefore I don't want to disable this message. If you're interested
> to get rid of it, it would be most helpful trying to track down how to
> find the global FAST_CWD pointer in W8.
If I understood the code correctly f_cwd_ptr is the location of
ntdll!RtlpCurDirRef and find_fast_cwd_pointer tries to find that
location. For some reason I couldn't get breakpoints working when
debugging cygwin1.dll so I did some disassembling and found the correct
location for ntdll!RtlpCurDirRef in Windows 8 version of ntdll (wow64).
Any hints for debugging the Cygwin dll itself as find_fast_cwd runs once
per session so it has been very difficult trying to get a working
breakpoint.
Teemu
prev parent reply other threads:[~2011-10-12 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 19:39 Teemu Nätkinniemi
2011-10-12 8:27 ` Corinna Vinschen
2011-10-12 20:45 ` Teemu Nätkinniemi [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=4E95FC38.1090500@gmail.com \
--to=tnatkinn@gmail.com \
--cc=cygwin-patches@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).