On 22/05/2025 14:15, Gary Liddle via Cygwin wrote:
Yesterday I updated Cygwin using  setup-x86_64 to the latest non test release, 
and bash —login would no longer start.

It turns out bash won’t start for me when a .profile runs a sub-command.

This is highlighted by:-

        gdb bash
        dll cygwin1.dll
        b timegm
        run
        bash-5.2$ echo foo
        foo
        bash-5.2$ a=`echo foo`

        Program received signal SIGSEGV, Segmentation fault.
        0x00007ffa5cb3ce31 in timegm () from D:\cygwin64\bin\cygwin1.dll
        (gdb)
        ...
        bash-5.2$ a=`xxx`
        bash: xxx: command not found
        
        Program received signal SIGSEGV, Segmentation fault.
        0x00007ffa5cb3ce31 in timegm () from D:\cygwin64\bin\cygwin1.dll
        (gdb)

        uname -a CYGWIN_NT-10.0-26100 garyl 3.7.0-0.98.gb39b510c1ce6.x86_64 
2025-05-18 15:52 UTC x86_64 Cygwin

[...]

Thanks for reporting this.


I am at a loss as to how to dig further because gdb doesn’t seem to want to go 
near timegm and I can’t see anything in the strace output that seems to point 
to anything useful.

The information in [1] may be helpful in investigating further with gdb.

[1] https://cygwin.com/faq.html#faq.programming.debugging-cygwin


--
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

Reply via email to