https://bugs.kde.org/show_bug.cgi?id=393284
--- Comment #4 from kdem...@protonmail.com --- Thanks but i was already aware of that linked page. In turn, relevant for Arch/Manjaro [given as you correctly state by default they do not have debug symbols] i have thrice read the associated page [1] https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces, & its associated page [2] https://wiki.archlinux.org/index.php/Core_dump#Examining_a_core_dump. I have also now read [3] `man coredumpctl` & [4] `coredumpctl --help`. From [2] i was able to see: ``` [kdemeoz@Lappy-XPS15 ~]$ coredumpctl list TIME PID UID GID SIG COREFILE EXE <<snipped for brevity>> Thu 2018-04-19 14:06:13 AEST 9260 1000 1000 6 missing /usr/bin/kwin_x11 Thu 2018-04-19 14:10:14 AEST 1229 1000 1000 6 missing /usr/bin/kwin_x11 Sat 2018-04-21 14:31:30 AEST 29658 1000 1000 6 truncated /usr/bin/kwin_x11 Sat 2018-04-21 17:00:26 AEST 32096 1000 1000 6 truncated /usr/bin/kwin_x11 Sat 2018-04-21 17:00:27 AEST 31811 1000 1000 6 truncated /usr/bin/kwin_x11 Sat 2018-04-21 17:14:33 AEST 31946 1000 1000 6 truncated /usr/bin/kwin_x11 Sat 2018-04-21 19:18:53 AEST 6444 1000 1000 6 truncated /usr/bin/kwin_x11 Sat 2018-04-21 19:19:27 AEST 29534 1000 1000 6 truncated /usr/bin/kwin_x11 Sat 2018-04-21 19:37:48 AEST 4066 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 14:24:41 AEST 23291 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 14:27:18 AEST 1285 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 22:43:22 AEST 19574 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 22:45:19 AEST 21322 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 22:45:20 AEST 21672 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 22:45:22 AEST 21542 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 23:53:39 AEST 1389 1000 1000 6 truncated /usr/bin/kwin_x11 Sun 2018-04-22 23:53:43 AEST 2817 1000 1000 6 truncated /usr/bin/kwin_x11 Mon 2018-04-23 00:40:35 AEST 5255 1000 1000 6 truncated /usr/bin/kwin_x11 Mon 2018-04-23 00:41:03 AEST 7165 1000 1000 6 truncated /usr/bin/kwin_x11 lines 13-50/50 (END) ``` ...& then via [3] "Example 2. Invoke gdb on the last core dump": ``` [kdemeoz@Lappy-XPS15 ~]$ coredumpctl gdb PID: 7165 (kwin_x11) UID: 1000 (kdemeoz) GID: 1000 (kdemeoz) Signal: 6 (ABRT) Timestamp: Mon 2018-04-23 00:40:50 AEST (11h ago) Command Line: /usr/bin/kwin_x11 --crashes 1 Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/session-c8.scope Unit: session-c8.scope Slice: user-1000.slice Session: c8 Owner UID: 1000 (kdemeoz) Boot ID: 4d57b850825045aaa73d73195fd923ef Machine ID: 3054f65cf0df4fa190579b2f767ba3aa Hostname: Lappy-XPS15 Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.4d57b850825045aaa73d73195fd923ef.7165.1524408050000000.lz4 (truncated) Message: Process 7165 (kwin_x11) of user 1000 dumped core. Stack trace of thread 7165: #0 0x00007f1382d3c860 n/a (n/a) <<snipped for brevity>> Reading symbols from /usr/bin/kwin_x11...(no debugging symbols found)...done. BFD: warning: /var/tmp/coredump-7lm5u3 is truncated: expected core file size >= 2484768768, found: 2147483648 [New LWP 7165] [New LWP 7369] [New LWP 7340] [New LWP 7169] [New LWP 7171] [New LWP 7172] [New LWP 7173] [New LWP 7188] [New LWP 7325] [New LWP 7170] Failed to read a valid object file image from memory. Core was generated by `/usr/bin/kwin_x11 --crashes 1'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f1382d3c860 in ?? () [Current thread is 1 (LWP 7165)] (gdb) bt #0 0x00007f1382d3c860 in ?? () Backtrace stopped: Cannot access memory at address 0x7fff46ccd2a0 (gdb) q [kdemeoz@Lappy-XPS15 ~]$ ``` It seems that i cannot make further progress unless i am able to overcome the missing debugging symbols, BUT they in turn IMO seem pointless given that `bt` is unable to access the data it needs anyway. Wrt [1], though i can understand specific parts of it, i'm afraid that i still can't quite grasp a firm picture of the total & exact steps i would need to perform for my situation. I regret therefore, that despite this bug being 100% reproducible on both my PCs, my inability to conform with your mandate to supply a Backtrace leaves me no practical alternative but to abandon my putative bug report. -- You are receiving this mail because: You are watching all bug changes.
