Details
-
Bug
-
Resolution: Out of scope
-
P2: Important
-
None
-
5.15.9, 6.3.0
Description
QProcess does not seem to work properly when running inside Docker on a M1 mac, but works great on Intel based macs. When enabling debug messages from qprocess_unix.cpp there is this output when running attached application with ./output /bin/ls:
QProcessPrivate::startProcess() QProcessPrivate::waitForStarted(-1) waiting for child to start (fd = 15) QProcessPrivate::processStarted() == true QProcessPrivate::waitForStarted() == true PWC main: returned from waitForStarted QProcessPrivate::waitForReadyRead(5000) QProcessPrivate::bytesAvailableInChannel(1) == 0 QProcessPrivate::readFromChannel(1, 0x4000220648 "...", 1) == 0 QProcessPrivate::bytesAvailableInChannel(2) == 0 QProcessPrivate::readFromChannel(2, 0x40002217d8 "...", 1) == 0 QProcessPrivate::waitForDeadChild() dead with exitCode 64 , crashed? true QProcessPrivate::killProcess()'
Exit code 64 probably means EX_USAGE. But directly calling execv() with same arguments seems to work.