subject:"\[filelight\] \[Bug 449688\] Filelight crash on directory scan start"

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-02-01 Thread Albert Astals Cid

https://bugs.kde.org/show_bug.cgi?id=449688 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/qt/q

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Jaak Ristioja

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #24 from Jaak Ristioja --- I can also confirm that the committed fix solves this issue. Thank you very much! :-) I'm using debug builds of Qt for mostly the same reasons: it helps debugging. More specifically, I think I turned on USE=debug

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Andreas Sturmlechner

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #23 from Andreas Sturmlechner --- (In reply to Thomas Bettler from comment #22) > originally debug is enabled for qtcore to produce meaninful backtraces for a > couple of bugs with digikam, kwin/plasma-integration, mesa/opencl, and >

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Thomas Bettler

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #22 from Thomas Bettler --- originally debug is enabled for qtcore to produce meaninful backtraces for a couple of bugs with digikam, kwin/plasma-integration, mesa/opencl, and others. :-) I never experienced such a runtime issue due to

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Andreas Sturmlechner

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #21 from Andreas Sturmlechner --- Why did you enable debug, anyway? -- You are receiving this mail because: You are watching all bug changes.

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Thomas Bettler

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #20 from Thomas Bettler --- well done :-) that fixed it for me -- You are receiving this mail because: You are watching all bug changes.

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=449688 Harald Sitter changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=449688 Harald Sitter changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #17 from Harald Sitter --- Right, I can reproduce the crash with a -debug build. -- You are receiving this mail because: You are watching all bug changes.

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Jaak Ristioja

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #16 from Jaak Ristioja --- Yes, possibly. -- You are receiving this mail because: You are watching all bug changes.

[filelight] [Bug 449688] Filelight crash on directory scan start

2023-01-01 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #15 from Harald Sitter --- I do wonder... Reading the code this may legitimately fail the assert in the code paths we are hitting. The reason it only happens for you is because you build with debug perhaps? -- You are receiving this mail

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-31 Thread Thomas Bettler

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #14 from Thomas Bettler --- (In reply to Andreas Sturmlechner from comment #12) > Regarding qtbase, it is split in Gentoo with filelight depending on qtcore, > qtgui and qtwidgets. Assuming toolchain, CFLAGS etc. are consistent > globally,

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-31 Thread Andreas Sturmlechner

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #13 from Andreas Sturmlechner --- (to be clear, filelight-22.12.0 - or previous versions - hasn't crashed for me in Gentoo) -- You are receiving this mail because: You are watching all bug changes.

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-31 Thread Andreas Sturmlechner

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #12 from Andreas Sturmlechner --- (In reply to Harald Sitter from comment #11) > (In reply to Thomas Bettler from comment #9) > > emerge --info > > I'd be more interested in the information for qtbase. emerge --info is global, unless user

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-31 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #11 from Harald Sitter --- (In reply to Thomas Bettler from comment #9) > Created attachment 154921 [details] > emerge_info.txt > > emerge --info I'd be more interested in the information for qtbase. The upstream commit isn't really a

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-31 Thread Thomas Bettler

https://bugs.kde.org/show_bug.cgi?id=449688 Thomas Bettler changed: What|Removed |Added Ever confirmed|0 |1 URL|

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-30 Thread Thomas Bettler

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #9 from Thomas Bettler --- Created attachment 154921 --> https://bugs.kde.org/attachment.cgi?id=154921=edit emerge_info.txt emerge --info -- You are receiving this mail because: You are watching all bug changes.

[filelight] [Bug 449688] Filelight crash on directory scan start

2022-12-30 Thread Thomas Bettler

https://bugs.kde.org/show_bug.cgi?id=449688 --- Comment #8 from Thomas Bettler --- Created attachment 154920 --> https://bugs.kde.org/attachment.cgi?id=154920=edit emerge_compile_log.txt no special flags applied -- You are receiving this mail because: You are watching all bug changes.