Hello,
Thanks amos, your Ipv6 patch works very well, but for now i have another
problem. There are many crashes with FD_WRITE_METHOD function.
here is the backtrace:
#0 0x00020d0e785a in write () from /usr/lib/libc.so.65.0
#1 0x00020fda254f in write (fd=163, buf=0x205099000,
The patch looks good.
An inexistant DNS name definitely should not crash the system by
assertion failure. The good behavior is to tolerate the problem and
print out the error log to notify the users. It's better to print out
a message before simply return -1.
Best,
Tianyin
On Mon, Jan 7, 2013
Hi Tianyin;
asserts are used to guard the code against logic errors; if they are
triggered in response to external input, then it is the result of a
bug showing up, not a normal response to that input.
The best way forward is to either to make the developers aware of this
or, even better, to
On 8/01/2013 8:06 p.m., Loïc BLOT wrote:
In my case, it seems the ASSERT is thrown when GetAddrInfo look at
inexistant DNS name. (in the backtrace the DNS name does'nt exists).
Before there is 2 conditions for IPv4 and IPv6. This function is called
before any helper i think
Le mercredi 09 janvier 2013 à 00:05 +1300, Amos Jeffries a écrit :
On 8/01/2013 8:06 p.m., Loïc BLOT wrote:
In my case, it seems the ASSERT is thrown when GetAddrInfo look at
inexistant DNS name. (in the backtrace the DNS name does'nt exists).
Before there is 2 conditions for IPv4 and IPv6.
On Jan 8, 2013, at 7:04 AM, Loïc Blot loic.b...@unix-experience.fr wrote:
Le mercredi 09 janvier 2013 à 00:05 +1300, Amos Jeffries a écrit :
On 8/01/2013 8:06 p.m., Loïc BLOT wrote:
In my case, it seems the ASSERT is thrown when GetAddrInfo look at
inexistant DNS name. (in the backtrace the
On 9/01/2013 2:04 a.m., Loïc Blot wrote:
Le mercredi 09 janvier 2013 à 00:05 +1300, Amos Jeffries a écrit :
On 8/01/2013 8:06 p.m., Loïc BLOT wrote:
In my case, it seems the ASSERT is thrown when GetAddrInfo look at
inexistant DNS name. (in the backtrace the DNS name does'nt exists).
Before
Hello,
i get crashes since migrating from Squid 3.1.22 to Squid 3.2.5 last
week. In 3.1.22 there are less crashes :s.
I want to use 3.2.X to improve the functionnalities. Squid is configured
with SquidGuard.
Do you have an idea ?
Here are the logs:
Page faults with physical i/o: 0
2013/01/07
Here is the backtrace:
#0 0x000206a8ebca in kill () from /usr/lib/libc.so.65.0
#1 0x000206af5791 in abort ()
at /usr/src/lib/libc/stdlib/abort.c:68
#2 0x000206a72e84 in __assert2 (file=Variable file is not
available.
) at /usr/src/lib/libc/gen/assert.c:52
#3 0x0066161c in
Hello,
at first time, only 10 squidGuard helpers are used. Next i increase the
amount because i thought squid doesn't have so many helpers, to this
limit 150/192.
But it was a big crash. I have posted the crash datas and my fix on
bugzilla (now no crash since the fix). Assert is a bad thing :(.
I didn't had much time to look at the back-trace.
Also I dont know what is your knowledge is about assert or other things.
I dont know about this specific one but.. in most cases it's there for a
reason.
It's there to make an assessment about the state of the code.
Maybe the server is not
In my case, it seems the ASSERT is thrown when GetAddrInfo look at
inexistant DNS name. (in the backtrace the DNS name does'nt exists).
Before there is 2 conditions for IPv4 and IPv6. This function is called
before any helper i think (Comm::ConnOpener::start), squidGuard doesn't
show anything
12 matches
Mail list logo
