4 ms·

The invalid system call issue is likely due to a recent Mac OS update. It turned out redbean was depending on a Mach system call when the intent was to only use

by jart 4y ago

The invalid system call issue is likely due to a recent Mac OS update. It turned out redbean was depending on a Mach system call when the intent was to only use the UNIX APIs which I believe will be stable since they're much more public. https://github.com/jart/cosmopolitan/issues/426 https://github.com/jart/cosmopolitan/issues/426 New 2.0.2 release available on https://redbean.dev https://redbean.dev which includes the fix.

brabel 4y ago
2.0.3 now :D and I can confirm it runs on my Mac (Monterey 12.4 (21F79))... Looks great!
- zimpenfish 4y ago
  Annoyingly, 2.0.3 appears broken on 12.5 Beta (21G5027d).
  - jart 4y ago
    Wow. Could you please open a GitHub issue with a `./redbean.com --ftrace` log? I only need the fifty or so lines of the log. Since that tells me which system call is likely the culprit. https://github.com/jart/cosmopolitan/issues https://github.com/jart/cosmopolitan/issues Alternatively you could email it to me: jtunney@gmail.com Thanks!
    - zimpenfish 4y ago
      It's an instant `Segmentation fault: 11` - although this might be because I'm on M1 (although it still happens under `arch -x86_64 bash` which forces it directly through Rosetta 2.) Seems I can't run `dtruss` or anything useful either to track it down further because of the new stringent SIP protections, sorry!
      - zimpenfish 4y ago
        Looks like people are already on this case: https://github.com/jart/cosmopolitan/issues/429 https://github.com/jart/cosmopolitan/issues/429