public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.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: Sat, 28 Dec 2013 09:02:00 -0000	[thread overview]
Message-ID: <83wqip2vs1.fsf@gnu.org> (raw)
In-Reply-To: <20131228031719.GC4532@adacore.com>

> Date: Sat, 28 Dec 2013 07:17:19 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> I would hate to see it all lost in the mailinglist archives, though.
> How about we turn this into either a comment in the code (my prefered
> option, most of the time), or a gdbint update (on the wiki), or even
> just a wiki page somewhere. We could open, if not already done,
> a section dealing with Windows-specific issues.

I can do that, please point me to the relevant places.

Btw, there's one other quite significant nuisance with using file
names that breach the 260-character limits: you can do almost nothing
with them, once they are created, except if you write your own
programs to deal with them.  It looks like none of the programs and
commands that come with Windows out of the box are able to handle such
file names.  You cannot delete them, neither from the Explorer nor by
using DEL from the shell prompt.  The Explorer silently and
inexplicably fails to copy directories which include such files.  So
you are basically stuck with them, unless you write your own programs
to delete/copy/rename them.  (I didn't try Cygwin: perhaps its file
utilities can also be a way out.)

So: children, don't try that at home!

  reply	other threads:[~2013-12-28  9:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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
2013-12-18 15:46     ` Eli Zaretskii
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 [this message]
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
2013-12-18  3:37 ` Yao Qi

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=83wqip2vs1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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).