On 07/21/2023 14:46, Martin Storsjö wrote:
On Fri, 21 Jul 2023, Cristian Adam wrote:
Right, lldb was using the DWARF debugging information
I've attached 3 screenshots of Qt Creator using lldb:
1. Unstripped MaxiDump.exe showed the bad source line and the correct
stacktrace (due to
On Fri, 21 Jul 2023, Cristian Adam wrote:
Right, lldb was using the DWARF debugging information
I've attached 3 screenshots of Qt Creator using lldb:
1. Unstripped MaxiDump.exe showed the bad source line and the correct
stacktrace (due to DWARF information)
2. Stripped MaxiDump.exe
On 07/21/2023 14:26, Cristian Adam via Development wrote:
On 07/21/2023 11:04, Martin Storsjö wrote:
- With LLDB: As LLDB supports both DWARF and PDB, it will prefer DWARF if such
debug info was found. As other toolchain files that are linked in happen to
have some DWARF in them, the executable
On 21/07/2023 11:01, Volker Hilsheimer via Development wrote:
How about conversion:
I, for one, would like to stop seeing magic conversions added into
QVariant, and keep breaking stuff at every Qt major release because we
realize we went overboard and have to remove features.
Now, one
On Thu, 20 Jul 2023, Cristian Adam via Development wrote:
WinDbg didn't work, but lldb.exe itself works:
lldb MaxiDump.exe --core MaxiDump.dmp
I've updated cristianadam/MaxiDump (github.com) with this new information.
FWIW, I didn't test minidumps, but I tested that PDBs currently do
> On 20 Jul 2023, at 16:17, Fabian Kosmale via Development
> wrote:
>> Hi everyone,
>>
>> something that came up during this year’s KDE Akademy was that we
>> believe Q_PROPERTY should be able to handle std::optional, such that you
>> get a null QVariant out of it if it has no value. The main
Hi all,
I don't like the "what _you_ should expect". IMNSHO, _we_ should expect
it to break only when _we_ add code that causes it to break. IOW: before
we enable this feature on the production CI for a given configuration X,
the submitter should have tried configuration X with a
