Hello, I am not the maintainer of libuhd, just tried to get some more information from the provided dmesg Code lines.
These end in some boost::asio functions: boost::asio::detail::scheduler::concurrency_hint() const at /usr/include/boost/asio/detail/scheduler.hpp:142 Unfortunately this allows no guess to where exactly this is called in libuhd. When I start qgrx inside a minimal VM I could not see a crash, but guess this needs some special hardware? If this is still an issue please provide - the exact steps until you receive a crash. - maybe the output which gets written when starting qgrx from a terminal - install systemd-coredump. This should produce in the journal some more information. A lot more information about how to retrieve a backtrace could be found here: https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard
