public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Unable to execute Cygwin application within UDF format
Date: Fri, 27 May 2022 17:43:29 +0900	[thread overview]
Message-ID: <20220527174329.648848d4fdd4800753b75b54@nifty.ne.jp> (raw)
In-Reply-To: <20220527133120.58530edd99f4a87c605b8a04@nifty.ne.jp>

On Fri, 27 May 2022 13:31:20 +0900
Takashi Yano wrote:
> On Fri, 27 May 2022 11:36:27 +0800
> Sam Lin wrote:
> > I will see the problem on WIN10 or WIN SERVER, the duplicate steps are as
> > follows:
> > 
> > 1. Write a simple code 'hello world'  program  and   compiled the
> > executable file using GCC.
> > 
> > //  hello.c
> > #include <stdio.h>
> > 
> > int main() {
> >     printf("Hello World\n");
> >     return 0;
> > }
> > 
> > $ gcc hello.c -o hello.exe
> > 
> > 2. Format the specified USB drive using command prompt.
> >   C:\> format <USB Drive Letter>: /fs:UDF /q
> > 
> > 3. Put the executable files hello.exe and cygwin1.dll into the UDF format
> > flash drive and execute.
> > We will find that the execution error occurs with cygwin v3.2.x and above.
> > 
> > F:\>hello.exe
> >       0 [main] hello (16224) F:\hello.exe: *** fatal error - add_item
> > ("\??", "/", ...) failed, errno 22
> > Stack trace:
> > Frame        Function    Args
> > 000FFFFCCE0  001800622EE (0018029F172, 0018027AE81, 00800000000,
> > 000FFFF8B40)
> > 000FFFFCCE0  0018004874A (00000000000, 000FFFFCCE0, 00180020010,
> > 000FFFFABD6)
> > 000FFFFCCE0  00180048782 (000FFFF9BD0, 00000000016, 00800000000,
> > 00000000001)
> > 000FFFFCCE0  001800E30BC (000FFFFCBD0, 000FFFFCDF0, 001800D7488,
> > 00000000000)
> > 000FFFFCCE0  00180133DC5 (001800D344A, 00000000000, 00000000000,
> > 00000000000)
> > 000FFFFCCE0  00180048DA5 (00000000000, 00000000000, 00000000000,
> > 00000000000)
> > 000FFFFFFF0  00180047856 (00000000000, 00000000000, 00000000000,
> > 00000000000)
> > 000FFFFFFF0  00180047904 (00000000000, 00000000000, 00000000000,
> > 00000000000)
> > End of stack trace
> > 
> > This error does not occur in v3.1.7.
> > Hope this will be resolved in the future.
> 
> This seems to happen if cygwin1.dll is placed in the root
> directly regardless of file system type.

I meant "root directory".

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2022-05-27  8:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  3:36 Sam Lin
2022-05-27  4:31 ` Takashi Yano
2022-05-27  8:43   ` Takashi Yano [this message]
2022-05-27  8:47   ` Sam Lin
2022-05-27  9:18     ` Takashi Yano
2022-05-27 10:51       ` Takashi Yano
2022-05-27 12:28         ` Takashi Yano
2022-05-27 12:36           ` Takashi Yano
2022-05-28 13:22             ` Ken Brown
2022-05-28 14:25               ` Takashi Yano
2022-05-27 17:41       ` Sam Edge

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=20220527174329.648848d4fdd4800753b75b54@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@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).