Bug#1116969: Acknowledgement (segmentation fault on successive "-client -debug PID" usage)

To: 1116969@bugs.debian.org
Subject: Bug#1116969: Acknowledgement (segmentation fault on successive "-client -debug PID" usage)
From: "kolAflash@kolahilft.de" <kolAflash@kolahilft.de>
Date: Wed, 1 Oct 2025 20:19:37 +0200
Message-id: <[🔎] e9c95f9b-51e5-4c86-84dd-f4666a673a32@kolahilft.de>
Reply-to: "kolAflash@kolahilft.de" <kolAflash@kolahilft.de>, 1116969@bugs.debian.org
In-reply-to: <[🔎] 64ed623e-795d-4881-828a-8774720bf7e4@kolahilft.de>
References: <[🔎] d977e5ad-d645-4531-acbb-44907a82682c@kolahilft.de> <handler.1116969.B.17593284434109442.ack@bugs.debian.org> <[🔎] 64ed623e-795d-4881-828a-8774720bf7e4@kolahilft.de> <[🔎] d977e5ad-d645-4531-acbb-44907a82682c@kolahilft.de>

Unfortunately there's no option to "Enable crash reporting" here:

Edit => Preferences => Environment => System

https://doc.qt.io/qtcreator/creator-how-to-turn-on-crash-reports.html

I guess this is, because the "Qt Group" may only accept crash reportsfrom their official QtCreator builds.




These might be related.

Starting debugger causes crash on MacOS (QtCreator 14.0.2)
https://bugreports.qt.io/browse/QTCREATORBUG-31805

Crash during debugger run (QtCreator-16.0.2)
https://bugreports.qt.io/browse/QTCREATORBUG-33080

Reply to:

References:
- Bug#1116969: segmentation fault on successive "-client -debug PID" usage
  - From: "kolAflash@kolahilft.de" <kolAflash@kolahilft.de>
- Bug#1116969: Acknowledgement (segmentation fault on successive "-client -debug PID" usage)
  - From: "kolAflash@kolahilft.de" <kolAflash@kolahilft.de>

Prev by Date: Processing of qtcreator_17.0.2-1_source.changes
Next by Date: qt6-declarative_6.9.2+dfsg-4_source.changes ACCEPTED into unstable
Previous by thread: Bug#1116969: Acknowledgement (segmentation fault on successive "-client -debug PID" usage)
Next by thread: Bug#1115396: kteatime: icon invisible in system tray
Index(es):
- Date
- Thread