From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Yao Qi'" <yao@codesourcery.com>, "'Pedro Alves'" <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] Fix cygwin compilation failure due to nameless LOAD_DLL_DEBUG_EVENT causes ntdll.dll to be missing
Date: Tue, 17 Dec 2013 08:43:00 -0000 [thread overview]
Message-ID: <002801cefb04$19a863b0$4cf92b10$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <52AF9D9C.4000908@codesourcery.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Yao Qi
> Envoyé : mardi 17 décembre 2013 01:41
> À : Pedro Alves
> Cc : Pierre Muller; gdb-patches@sourceware.org
> Objet : Re: [RFA] Fix cygwin compilation failure due to nameless
> LOAD_DLL_DEBUG_EVENT causes ntdll.dll to be missing
>
> On 12/17/2013 02:05 AM, Pedro Alves wrote:
> > At this level we're thinking in terms of Win32 debug API, and
> > it's irrelevant what Cygwin thinks is the Posix path of
> > ntdll.dll. If this is indeed ntdll.dll, then the following
> > windows_make_so call will then do that conversion before
> > recording the dll name.
>
> My point is we use cygwin_conv_path to convert the path to type "char
> *"
> and then compare whether it is ntdll.dll.
As Pedro explained, I don't think this is useful here,
because we only check the filename part of the DLL,
this is not changed by the cygwin_conv_path which only converts
Windows OS paths into cygwin paths.
Moreover, windows_make_so expect a windows OS path,
which is copied into so_original_name
while so_name gets the return value of cygwin_conv_path.
Thus I would expect that your idea to call cygwin_conv_path
inside windows_ensure_ntddl_loaded would lead to a
failure at the start of the windows_make_so which calls the
Win32 API function FindFirstFile.
I hope this clarifies the point.
Pierre Muller
next prev parent reply other threads:[~2013-12-17 8:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 22:41 Pierre Muller
2013-12-16 2:21 ` Yao Qi
2013-12-16 18:05 ` Pedro Alves
2013-12-17 0:43 ` Yao Qi
2013-12-17 8:43 ` Pierre Muller [this message]
2013-12-18 3:37 ` Yao Qi
[not found] <52ab8d0e.8aa2420a.30ff.ffffd8f1SMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-16 17:13 ` Pedro Alves
2013-12-16 22:50 ` Pierre Muller
2013-12-18 11:20 ` Corinna Vinschen
[not found] ` <83bo0ecgdw.fsf@gnu.org>
2013-12-18 16:07 ` Corinna Vinschen
2013-12-18 17:03 ` Eli Zaretskii
2013-12-18 17:18 ` Corinna Vinschen
2013-12-18 17:29 ` Eli Zaretskii
2013-12-18 17:31 ` Corinna Vinschen
2013-12-18 18:19 ` Eli Zaretskii
2013-12-18 19:18 ` Corinna Vinschen
2013-12-18 20:01 ` Eli Zaretskii
2013-12-18 20:54 ` Corinna Vinschen
2013-12-19 18:33 ` Eli Zaretskii
2013-12-28 3:17 ` Joel Brobecker
2013-12-28 9:02 ` Eli Zaretskii
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='002801cefb04$19a863b0$4cf92b10$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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