Can we print fatal Qt messages despite `abort()`?

As outlined in Troubleshooting — pytest-qt documentation, when Qt calls abort, often the user doesn't have any useful information due to pytest's output capturing.

I can see two ways around this, which might be worth exploring:

• Disable pytest output capturing while creating a QApplication
• Use qInstallMessageHandler to set up a custom message handler which prints some messages (fatal ones, at least) to a separate non-captured output stream (like faulthandler support in pytest)

Not sure if (especially the first one) could get too noisy though, Qt might print some unrelated stuff at startup maybe...

Start with the Troubleshooting — pytest-qt documentation section and the code path that creates a QApplication. Compare disabling pytest output capturing with using qInstallMessageHandler to send fatal Qt messages to a separate non-captured stream, then verify fatal messages remain visible without excessive unrelated startup output.