https://bugs.kde.org/show_bug.cgi?id=466229
Stephan Kulow changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #9 from Stephan Kulow ---
https://invent.kde.org/games/kpat/-/merge_requests/44
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466229
Stephan Kulow changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #8 from Stephan Kulow ---
./bin/kpat --solve 14 --start 5 will reproduce the crash - I just had bad luck
before.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #7 from Stephan Kulow ---
I managed to trigger it. I had to make my computer busy (your's is recompiling
the world, right? :) and play in one suit variant and click like a maniac.
==2602== Thread 9 SolverThread:
==2602== Invalid write of s
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #6 from Stephan Kulow ---
FORTIFY won't make a difference - and valgrind is silent.
Can you please run kpat --solve 15 --end 1000 (this is two suits variant). What
variant are you playing anyway?
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=466229
Stephan Kulow changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #4 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to Duncan from comment #3)
> I'll have to look up again how to build unstripped, with debugging enabled
This is more like it. (The - bit is gentoo's normal live-git package
version-nu
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #3 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to Stephan Kulow from comment #2)
> Hi, can you export KDE_DEBUG=1 before starting it from console? Then
> something useful should appear in coredumpctl (typing from memory as I'm not
> havi
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #2 from Stephan Kulow ---
Hi, can you export KDE_DEBUG=1 before starting it from console? Then something
useful should appear in coredumpctl (typing from memory as I'm not having a
computer around).
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #1 from Duncan <1i5t5.dun...@cox.net> ---
Bisecting confirms it's the new solver. 417bdc2ec (the new solver) bad.
3c581787e (the commit previous to that) seems to be fine. (Well, at least it
played a full round without segfaulting, tho as I
11 matches
Mail list logo
