Control: tags -1 moreinfo Control: retitle -1 [hexchat] Receives unexpected SIGTERM
On Thu, Feb 14, 2019 at 03:06:32AM +0100, Synthea wrote: > Package: hexchat > Version: 2.14.2-3~bpo9+1 > Severity: important > > Noticed this problem while running hexchat in gdb > Thread 1 "hexchat" received signal SIGTERM, Terminated. > raise (sig=15) at ../sysdeps/unix/sysv/linux/raise.c:51 So this is telling you something (maybe hexchat itself, though likely not) sent a SIGTERM signal to hexchat. Are you low on memory (since that could cause the OOM killer to send a SIGTERM to hexchat)? Please run the "thread apply all bt" command to get a backtrace so we can have more of an idea what's going on > 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. This is not the error. This is just GDB trying to print out the source code corresponding to where the debugger as stopped, but since you don't have glibc's source code unpacked in a location it can find, it instead prints this message to tell you it can't find the source. James
