Re: [squid-users] Assertion failed (mempool.cc)

2020-07-19 Thread Gabor Berczi
On Jul 18, 2020, at 11:15 PM, Alex Rousskov wrote: > I would try building the previous one again, using the exact same > procedure as you are using to build the new executable. Does the freshly > rebuilt old executable start OK? If yes, rebuild the new one from a > fresh directory. Just in case.

Re: [squid-users] Assertion failed (mempool.cc)

2020-07-18 Thread Alex Rousskov
On 7/18/20 11:43 AM, Gabor Berczi wrote: > newly compiled squid executables don't > start. The previous one does. Where do I start looking? I would try building the previous one again, using the exact same procedure as you are using to build the new executable. Does the freshly rebuilt old execut

Re: [squid-users] Assertion failed (mempool.cc)

2020-07-18 Thread Gabor Berczi
On Jul 18, 2020, at 7:59 PM, Amos Jeffries wrote: Are you building in a clean build directory from a clean set of sources? Yes. What OS are you building on? FreeBSD 8.4 amd64 but all of it is irrelevant. I know this is PEBKAC, but what I'm interested in is where/why. Already tried diff

Re: [squid-users] Assertion failed (mempool.cc)

2020-07-18 Thread Amos Jeffries
On 19/07/20 3:43 am, Gabor Berczi wrote: > Greets. > > I've fucked up something and now newly compiled squid executables don't > start. The previous one does. Where do I start looking? > Are you building in a clean build directory from a clean set of sources? What OS are you building on? Are y

[squid-users] Assertion failed (mempool.cc)

2020-07-18 Thread Gabor Berczi
Greets. I've fucked up something and now newly compiled squid executables don't start. The previous one does. Where do I start looking? Assertion failed: (aLabel != NULL && aSize), function MemImplementingAllocator, file MemPool.cc, line 394. Program received signal SIGABRT, Aborted. [Swi