Menu

#190 ksh readonly.exe exited on signal 11

open
nobody
2026-01-26
2026-01-15
No

During the build of cde, I'm noticing a readonly.exe exited on signal 11 (without coredump), which seemingly is part of ksh93...

Would you possibly consider updating ksh93 in cde to 1.0.10 ?

As it currently sits at 1.0.3 (3300d665a097c8921d69c67f33527c1033c32d1a)

Discussion

  • Pascal de Bruijn

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,3 +1,5 @@
     During the build of cde, I'm noticing a readonly.exe exited on signal 11 (without coredump), which seemingly is part of ksh93...
    
     Would you possibly consider updating ksh93 in cde to 1.0.10 ?
    +
    +As it currently sits at 1.0.3 (3300d665a097c8921d69c67f33527c1033c32d1a)
    
     
  • Pascal de Bruijn

    I've tested ksh93 outside of cde, and both 1.0.3 AND 1.0.10 still have the readonly.exe signal 11...

    So this isn't a CDE issue, but likely ksh93 upstream, and not fixed yet in the latest release...

     
  • Pascal de Bruijn

    And this is still reproducible with gcc 13.4...

     
  • Pascal de Bruijn

    As an aside, I did make a diff of ksh-1.0.3 and ksh-1.0.10 and tried applying that to CDE, which ended up with rejects in src/cmd/ksh/sh/xec.c and src/lib/libast/features/aso.

     
  • Pascal de Bruijn

    After some more experimentation:
    Patching to 1.0.4 seems possible with no rejects.
    Patching up to 1.0.8 seems possible with only 2 rejects (in xec.c)...
    Patching from 1.0.9 introduces 16 rejects (in aso)...

     

Log in to post a comment.

MongoDB Logo MongoDB