https://bugs.kde.org/show_bug.cgi?id=423963
Christoph Cullmann <cullm...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cullm...@kde.org
--- Comment #2 from Christoph Cullmann <cullm...@kde.org> ---
Hi,
I have the same issue with Qt 6.1 (current branch state of today).
(and I have this since at least 6.0)
Interesting enough, it doesn't happen for all our QProcess::start calls :/
valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0
== (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed.
host stacktrace:
==1115104== at 0x58041B2A: show_sched_status_wrk (m_libcassert.c:406)
==1115104== by 0x58041C47: report_and_quit (m_libcassert.c:477)
==1115104== by 0x58041DD7: vgPlain_assert_fail (m_libcassert.c:543)
==1115104== by 0x5809AB4F: vgPlain_client_syscall (syswrap-main.c:1980)
==1115104== by 0x5809617A: handle_syscall (scheduler.c:1208)
==1115104== by 0x58098177: vgPlain_scheduler (scheduler.c:1526)
==1115104== by 0x580E38D0: thread_wrapper (syswrap-linux.c:101)
==1115104== by 0x580E38D0: run_a_thread_NORETURN (syswrap-linux.c:154)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable syscall 56 (lwpid 1115104)
==1115104== at 0x83E2A9D: syscall (in /usr/lib/libc-2.33.so)
==1115104== by 0x7E48636: forkfd (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/libQt6Core.so.6)
==1115104== by 0x7E2F881: QProcessPrivate::startProcess() (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/libQt6Core.so.6)
==1115104== by 0x7E2A4B9:
QProcessPrivate::start(QFlags<QIODeviceBase::OpenModeFlag>) (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/libQt6Core.so.6)
==1115104== by 0x15E54F9: main (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/a3c)
client stack range: [0x1FFEFE9000 0x1FFF000FFF] client SP: 0x1FFEFFE028
valgrind stack range: [0x10033B8000 0x10034B7FFF] top usage: 8328 of 1048576
valgrind version is valgrind-3.16.1, current Manjaro valgrind package.
Actually QProcess start code seems "normal", just like: (m_serverProcess ==
QProcess)
// try to startup the server, output its sever to stdout/err
m_serverProcess.setProcessChannelMode(QProcess::ForwardedChannels);
const QString program = arguments.takeFirst();
m_serverProcess.start(program, arguments, QProcess::ReadOnly);
if (!m_serverProcess.waitForStarted()) {
Ur::printf(Ur::Fatal, "Unable to start temporary server.");
}
Interesting enough, if I skip this process startup call (that happens in our
main shortly after the QApplication is created,
later calls that trigger more process starting work :/
I tried to avoid any special stuff we only do there, like the
m_serverProcess.setProcessChannelMode(QProcess::ForwardedChannels);
but that still happens.
--
You are receiving this mail because:
You are watching all bug changes.
