Re: Debugging ports

Well, 11-STABLE now has LLVM 5.0 too, so it should work as well as in head. I actually tried it on the recent 11-STABLE. On 17-10-18 10:03:49, Guido Falsi wrote: On 10/18/2017 09:59, Piotr Kubaj wrote: According to https://wiki.freebsd.org/lldb, it should work just fine on amd64, apart from

Re: Debugging ports

According to https://wiki.freebsd.org/lldb, it should work just fine on amd64, apart from kernel debugger. I suppose there should be some improvements for other archs too, since that page was updated 1.5 years ago :) On 17-10-18 09:54:05, Guido Falsi wrote: On 10/18/2017 09:52, Piotr Kubaj

Re: Debugging ports

Shouldn't lldb be the replacement for gdb in base? On 17-10-18 09:47:25, Guido Falsi wrote: On 10/18/2017 06:33, Jan Beich wrote: Kubilay Kocak writes: On 10/18/17 8:29 AM, Jan Beich wrote: Guido Falsi writes: On 10/17/2017 23:11, Guido Falsi

Re: Debugging ports

I think I got it. It turns out that it's our gdb in base that can't read the debug info. lldb and gdb from ports do it just fine. I also thought about recompiling library dependecies, but something didn't fit in, because not only the libraries calls were not there, but the calls from the port

Debugging ports

Hi all, I am preparing a new port. However, I hit an assertion fail when starting the binary. The developer is willing to help me, provided that I send him backtrace and values from the structure that hits assertion failure. Thing is, recompiling with WITH_DEBUG doesn't help (I only get

Re: FreeBSD Port: MailScanner-5.0.3

After your commit, I now get an error during staging: (00:00:54) === (00:00:54) === (00:00:54) ===> Staging for MailScanner-5.0.3_1 (00:00:54) ** Missing

Re: www/lighttpd 1.4.45 broken mod_fastcgi for PHP

Could you send me a truss(1) output of the relevant process? On 17-03-01 11:36:02, Miroslav Lachman wrote: > Piotr Kubaj wrote on 2017/03/01 11:13: > > If FPM works fine, it looks to me more like PHP error than Lighttpd's. > > Could you use truss(1) on Lighttpd's process to obtain more

Re: www/lighttpd 1.4.45 broken mod_fastcgi for PHP

If FPM works fine, it looks to me more like PHP error than Lighttpd's. Could you use truss(1) on Lighttpd's process to obtain more information? On 17-03-01 10:56:29, Miroslav Lachman wrote: > Piotr Kubaj wrote on 2017/03/01 08:59: > > Hi, > > > > I use Lighttpd 1.4.45_1 on 11.0-RELEASE with

Re: www/lighttpd 1.4.45 broken mod_fastcgi for PHP

Hi, I use Lighttpd 1.4.45_1 on 11.0-RELEASE with mod_fastcgi and php-cgi. There are no problems with this setup. Are you sure php-cgi processes are running are the socket file is present? On 17-03-01 00:36:46, Miroslav Lachman wrote: > Hi, > I upgraded from 1.4.44 to 1.4.45_1 and after service