Unable to execute Cygwin application within UDF format

Sam Lin samlin0925@gmail.com
Fri May 27 08:47:09 GMT 2022


Hi ,

I have also successfully executed that is to move cygwin1.dll to the root
directory to execute.

Will cygwin1.dll be supported to execute in UDF format in the future?
Thanks,
Sam

Takashi Yano <takashi.yano@nifty.ne.jp> 於 2022年5月27日 週五 下午12:32寫道:

> 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.
>
> --
> Takashi Yano <takashi.yano@nifty.ne.jp>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>


More information about the Cygwin mailing list