https://bugs.kde.org/show_bug.cgi?id=400478
--- Comment #2 from Greg Lepore <g...@rhobard.com> --- Apparently no backtrace is created: lepore@lepore-desktop:~$ install kde-spectacle-dbgsym The following NEW packages will be installed: kde-spectacle-dbgsym 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2,290 kB of archives. After unpacking 2,406 kB will be used. Get: 1 http://archive.neon.kde.org/user bionic/main amd64 kde-spectacle-dbgsym amd64 18.08.2-0xneon+18.04+bionic+build11 [2,290 kB] Fetched 2,290 kB in 3s (700 kB/s) Selecting previously unselected package kde-spectacle-dbgsym. (Reading database ... 341564 files and directories currently installed.) Preparing to unpack .../kde-spectacle-dbgsym_18.08.2-0xneon+18.04+bionic+build11_amd64.ddeb ... Unpacking kde-spectacle-dbgsym (18.08.2-0xneon+18.04+bionic+build11) ... Setting up kde-spectacle-dbgsym (18.08.2-0xneon+18.04+bionic+build11) ... lepore@lepore-desktop:~$ gdb spectacle GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from spectacle...Reading symbols from /usr/lib/debug/.build-id/a5/7a982d244fe13cc89cf05e1ab19ddbae633e7a.debug...done. done. (gdb) run Starting program: /usr/bin/spectacle [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe39bb700 (LWP 29777)] [New Thread 0x7fffe0e9a700 (LWP 29778)] [Thread 0x7fffe39bb700 (LWP 29777) exited] [Thread 0x7fffe0e9a700 (LWP 29778) exited] [Inferior 1 (process 29768) exited normally] (gdb) thread apply all backtrace (gdb) thread apply all bt (gdb) Similarly, valgrind doesn't appear to show anything: cat spectacle ==31144== Memcheck, a memory error detector ==31144== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==31144== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==31144== Command: spectacle ==31144== Parent PID: 29849 ==31144== ==31144== ==31144== HEAP SUMMARY: ==31144== in use at exit: 379,866 bytes in 6,602 blocks ==31144== total heap usage: 153,205 allocs, 146,603 frees, 2,816,962,213 bytes allocated ==31144== ==31144== LEAK SUMMARY: ==31144== definitely lost: 632 bytes in 5 blocks ==31144== indirectly lost: 9,629 bytes in 62 blocks ==31144== possibly lost: 368 bytes in 1 blocks ==31144== still reachable: 369,237 bytes in 6,534 blocks ==31144== suppressed: 0 bytes in 0 blocks ==31144== Rerun with --leak-check=full to see details of leaked memory ==31144== ==31144== For counts of detected and suppressed errors, rerun with: -v ==31144== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) I guess it's possible that spectacle disappearing when the Copy to Clipboard button is click is how it's supposed to work? However, nothing is copied to the clipboard. -- You are receiving this mail because: You are watching all bug changes.
