Samuel Thibault, le dim. 28 mai 2023 13:16:15 +0200, a ecrit: > Sergey Bugaev, le dim. 28 mai 2023 13:32:12 +0300, a ecrit: > > The port error is interesting; 82650 is clearly not a port name, so > > it's not a port use-after-free / double free, it's some bad/invalid > > memory. Hmm. Is something overwriting our TCB? > > That could be. That could also explain the issues I'm getting with stack > protection. > > > Do you think this is happening after running a signal / RPC > > interruption? Or after a timeout? Is there any easy way to reproduce > > this? > > You can trap on the mach_port_deallocate warning case, or even in kdb > by setting mach_port_deallocate_debug to TRUE.
FI bash-static doesn't seem affected, that's why my image uses it as /bin/bash. But you can run /bin/bash.real and run ls from there, that's enough to trigger the bug. Samuel
