Closed Zombie-Ryushu closed 4 years ago
To see full useful backtraces you need to install debug symbols - https://spectrum.im/documentation/management/getting_backtrace.html
The problem is, my Distribution optomizes out the debug symbols. What I am going to well, try and do, is get you links to the libpurple plugin's github, then try and recompile with debug symbols enabled.
Most distributions have special packages with debuginfo
I'm finding and installing that now.
All listed libraries should have debug symbols installed and loaded to see code lines, not random numbers
Anyway it looks like crash in libmsn-pecan, so you may only need its debug symbols
0 0x00007fffeab7d6f7 in out_cmd (cmdproc=0x1d16790, cmd=0x230e220) at notification.c:418
cb = <optimized out>
trans = <optimized out>
__func__ = "msn_cmdproc_process_cmd"
cmd_conn = 0xf86e90
cur = 0x1e60fb0 "OUT"
next = 0x1e60fb5 ""
old_rx_buf = 0x1e60fb0 "OUT"
cur_len = <optimized out>
__func__ = "parse_impl"
conn = 0xf86e90
size = 5
error = 0x0
awesome! Now you can show this to libmsn-pecan developer and he will clearly understand the bug :) As there are no spectrum symbols it is not a spectrum issue
Strange Segfaults in libpurple backend when using the libmsn-pecan with the Escargot. spectrum2_libpu[18077]: segfault at 0 ip (null) sp 00007ffe7baaceb8 error 14 in spectrum2_libpurple_backend[400000+3e000]