https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/pal |https://invent.kde.org/game
https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
CC||rlgl...@netzero.com
--- Comment #20 from Al
https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=398416
Peter Hillier-Brook changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/pal
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #16 from Albert Astals Cid ---
https://phabricator.kde.org/D16118
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=398416
Christoph Feck changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=398416
Peter Hillier-Brook changed:
What|Removed |Added
Attachment #115148|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #11 from Christoph Feck ---
The 'gdb' log from comment #8 shows that Palapeli already crashed. But after
that, you need to use the 'bt' command to show the backtrace.
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #10 from Peter Hillier-Brook ---
I didn't forget the 'bt'. It was the "make it crash" that stumped me. How would
you suggest that I do this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #9 from Christoph Feck ---
You forgot the 'bt' command in gdb to actually get the backtrace.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398416
Peter Hillier-Brook changed:
What|Removed |Added
Attachment #114862|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #7 from Albert Astals Cid ---
Arg, you have an old valgrind that doesn't like new Qt.
Can you try with
gdb palapeli
run
make it crash
bt
attach here the output
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=398416
Peter Hillier-Brook changed:
What|Removed |Added
CC||p...@hbsys.plus.com
--- Comment #6 from P
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #5 from Albert Astals Cid ---
Can you run the program thorugh valgrind in a terminnal
valgrind palapeli
and attach the output?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #4 from Peter Hillier-Brook ---
Sorry about the duff screenshot. It showed that there was no useful backtrace
and I'm presently unable to reproduce the crash since installing the debug
package. Also, all my completed puzzles are no longer av
https://bugs.kde.org/show_bug.cgi?id=398416
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
--- Comment #3 from Albert As
https://bugs.kde.org/show_bug.cgi?id=398416
--- Comment #2 from Peter Hillier-Brook ---
Created attachment 114862
--> https://bugs.kde.org/attachment.cgi?id=114862&action=edit
Screenshot of bug assistant output.
Debug symbols installed, but still no useful crash information. Dialogue box
attac
https://bugs.kde.org/show_bug.cgi?id=398416
Christoph Feck changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=398416
Peter Hillier-Brook changed:
What|Removed |Added
Platform|Other |Debian testing
--
You are receiving this
22 matches
Mail list logo