https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #18 from pascal lacroix ---
Thanks,
"Now whole core/apps and core/showfoto port of Q_FOREACH to C++17::for() are
done."
Just build and run nicely.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #17 from caulier.gil...@gmail.com ---
Maik,
Now whole core/apps and core/showfoto port of Q_FOREACH to C++17::for() are
done.
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #16 from caulier.gil...@gmail.com ---
Maik,
Now whole core/utilities port of Q_FOREACH to C++17::for() is done.
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492686
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||8.5.0
Sentry Crash|8.5.0
https://bugs.kde.org/show_bug.cgi?id=492686
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Sentry Crash|
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #14 from pascal lacroix ---
I recompiled with your latest settings as requested.
Digikam no longer crashes.
By observing the display, I realize another small problem witch is perhaps
related, see attachment.
Good evening and thank you.
-
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #13 from pascal lacroix ---
Created attachment 173369
--> https://bugs.kde.org/attachment.cgi?id=173369&action=edit
display of thumbnails do not display frame
By observing the display, I realize another small problem with the display of
t
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #12 from caulier.gil...@gmail.com ---
Maik,
Just for info, whole code in core/libs are now ported from Q_FOREACH to
C++17::for().
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #11 from Maik Qualmann ---
Pascal, please compile the latest git/master version and report if the problem
can still be reproduced.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #10 from Maik Qualmann ---
Git commit f001ceb79c4f1a96208c55e318f0809a232814a7 by Maik Qualmann.
Committed on 05/09/2024 at 20:24.
Pushed by mqualmann into branch 'master'.
fix crash in updateChangedPAlbums()
M +6-4core/libs/album
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #9 from caulier.gil...@gmail.com ---
yes, probably. make a copy mask some concurrency problems difficult to
reproduce but not impossible to see.
The C++17::for() port will certainly introduce some regression which will force
to fix after all.
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #8 from Maik Qualmann ---
I think it's clear, Q_FOREACH always made a copy, we remove an entry that is
still being processed in the for loop, either via iterator or by making a copy.
Maik
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #7 from Maik Qualmann ---
Interesting that it crashes there, I can't reproduce it, but d->changedPAlbums
is the corresponding QSet (QHash). Probably accessed from different threads at
the same time.
Maik
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #6 from caulier.gil...@gmail.com ---
Maik,
At the code revision reported by Pascal, the AlbumManager was already patch
about Q_FOREACH migration to C++17::for() :
https://invent.kde.org/graphics/digikam/-/blob/f55ba145e2ca199d7d854ef959c955
https://bugs.kde.org/show_bug.cgi?id=492686
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #4 from pascal lacroix ---
With bt :
Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
0x7bd01391af37 in QHashData::nextNode(QHashData::Node*) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0 0x7bd01391af3
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #3 from Maik Qualmann ---
Only the messages after the crash are interesting, for this you have to type bt
+ enter, please post the messages that then appear.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492686
--- Comment #2 from pascal lacroix ---
revision :
https://invent.kde.org/graphics/digikam/commit/f55ba145e2ca199d7d854ef959c95529abab9263
I am not sure to give the backtrace as your request with the right methode but
...
Under gdb :
pascalou@pascalo
https://bugs.kde.org/show_bug.cgi?id=492686
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=492686
Bug Janitor Service changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail bec
20 matches
Mail list logo
