M mistwang LiteSpeed Staff Aug 3, 2008 #21 Aug 3, 2008 #21 You have to locate the core file first. then run command gdb <path_to_lshttpd> <path_to_core_file> then type gdb command bt if you create a symbolic link from your GDB to /usr/bin/gdb, LSWS will include the gdb output in the bug report email.
You have to locate the core file first. then run command gdb <path_to_lshttpd> <path_to_core_file> then type gdb command bt if you create a symbolic link from your GDB to /usr/bin/gdb, LSWS will include the gdb output in the bug report email.
P palb Well-Known Member Dec 23, 2008 #22 Dec 23, 2008 #22 mistwang said: You have to locate the core file first. then run command gdb <path_to_lshttpd> <path_to_core_file> then type gdb command bt if you create a symbolic link from your GDB to /usr/bin/gdb, LSWS will include the gdb output in the bug report email. Click to expand... I haven't done this yet but I need to do this to understand why it's restarted. What is the core file? Is that bin/lshttpd?
mistwang said: You have to locate the core file first. then run command gdb <path_to_lshttpd> <path_to_core_file> then type gdb command bt if you create a symbolic link from your GDB to /usr/bin/gdb, LSWS will include the gdb output in the bug report email. Click to expand... I haven't done this yet but I need to do this to understand why it's restarted. What is the core file? Is that bin/lshttpd?
