On 5/1/20 8:04 PM, Boris Faure wrote:
On 20-05-01 13:04, leoutat...@gmx.fr wrote:
On 5/1/20 12:48 PM, Boris Faure wrote:
On 20-05-01 12:34, leoutat...@gmx.fr wrote:
On 5/1/20 11:23 AM, Boris Faure wrote:
On 20-05-01 11:11, leoutat...@gmx.fr wrote:
Since last efl enlightenment terminology git versions (1.24),
terminology crashes after 4 seconds.
segmentation fault (core dumped) terminology
Could you please provide us with a backtrace from the core dumps?
It might be as simple as the following if the core dump is called
'core':
$ gdb /usr/bin/terminology core 2>&1 | tee ~/ty_gdb.txt
(gdb) handle SIG33 pass nostop noprint
(gdb) set pagination 0
(gdb) bt full
(gdb) thread apply all bt
(gdb) quit
And then give us ~/ty_gdb.txt
ty_gdb.txt
GNU gdb (GDB) 9.1
Reading symbols from /usr/bin/terminology...
Reading symbols from /usr/lib/debug/usr/bin/terminology.debug...
/home/fre/core: No such file or directory.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) bt full
No stack.
(gdb) thread apply all bt
(gdb) quit
The core file was not there.
You need to find where it was stored.
You can have a look at `/proc/sys/kernel/core_pattern`. It might be
stored in journald.
I found /proc/sys/kernel/core_pattern
It just contains /usr/lib/systemd/systemd-coredump
You need to play with coredumpctl.
# coredumpctl list
If terminology is the last one, then do the following:
# coredumpctl debug core 2>&1 | tee ~/ty_gdb.txt
(gdb) handle SIG33 pass nostop noprint
(gdb) set pagination 0
(gdb) bt full
(gdb) thread apply all bt
(gdb) quit
# coredumpctl list ---> terminology is the last one but i get:
# coredumpctl debug core 2>&1 | tee ~/ty_gdb.txt
No match found.
--
Maderios
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
