New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeBSD core dump #646
Comments
The error is stating that the file
I'm not sure how FreeBSD's malloc works, but this seems to be a configuration issue with your operating system and not a problem in ZNC. Please refer to the man page for malloc.conf |
Also, that's not a core dump and there are no write() calls in there (why do you think it is whining about malloc?). If you want to report a crash, grab gdb and get a backtrace (gdb znc, run, bt, bt full) |
it's whining about malloc because on freebsd /etc/malloc.conf does not exist and that's a kdump the freebsd equivalent to gdb I can see the errors without the need of gdb. |
If you have an error message then it would be nice to tell us about that error message. Believe it or not, error messages could actually contain useful information. Also, no. kdump is not the freebsd equivalent to gdb. The freebsd equivalent to gdb is gdb. The freebsd equivalent to strace is kdump. |
[root@kurobachan /usr/local/bin]# gdb ./znc Program received signal SIGSEGV, Segmentation fault. |
Did I point you at http://wiki.znc.in/Debugging already? Please read it. You didn't provide neither debug symbols to gdb, nor stack trace to us. |
[root@kurobachan /usr/local/bin]# gdb ./znc (gdb) handle SIGPIPE nostop Program received signal SIGSEGV, Segmentation fault. |
It's still compiled without debug symbols... |
GNU gdb 6.1.1 [FreeBSD] is too old, you can install new version gdb V8.1 to solve this problem pkg install gdband add /usr/local/bin/gdb to your PATH environment |
znc 1.5 is whining about malloc missing on freebsd 10 as seen in this core dump http://pastebin.com/jTxJQTpt
The text was updated successfully, but these errors were encountered: