Hi On 25-05-2025 07:21, Urs Fleisch wrote:
I tested it with kid3-qt. I would say that using the attached Kid3.conf with `KID3_CONFIG_FILE=~/Downloads/Kid3.conf kid3-qt` should be enough to reproduce the issue, but I never could (neither with copying the configuration to ~/.config/Kid3/Kid3.conf). I have Debian testing with KDE, the same package versions as in the report. I normally have a resolution of 31840x2160 at 150%, but I also tried to reproduce it with lower resolutions.
Hmm, interesting. I recently had other issues because of relative low resolution [1], my resolution is 1920x1080, but maybe because of my settings (rather big font), it may effectively be less.
[1] https://salsa.debian.org/reproducible-builds/reproducible-website/-/issues/61#note_554571
So what you could do is set a breakpoint in all these lines (58, 506, 530) to check if this code is run in the case of a crash and compare the address of widgetItem with the address of gap_item on the stack.
Although I'm a Debian Developer, I have very little experience with debugging code like that. I would need some hints how to achieve those things. Is it easy to say how to do that? Is it just as simple as starting kid3-qt under gdb, some call to set the breakpoint, type "run" and then ... I don't know...
You would have to install the debug symbol and source packages of qtbase to do so.
I'm using https://debuginfod.debian.net/ to get all debug symbols, but it's not sure if I need the source than too. Do you know? If yes, where should I put the source and/or how do I tell gdb?
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
