Hi Alex,
> So where does this misalignment originate from? Properly addressing this
bug probably requires answering this question.
Let's discuss it on Squid Bugzilla, I have already mentioned the bug above,
the bug number is 5008
> Please note that there are GCC v4 bugs that might be relevant h
FTR: hindsight1 runs v4.8 despite the email subject saying "3.5.21".
On 11/11/19 9:34 PM, hindsight1 wrote:
> thank you for your reply
Thank you for detailing the problem. The best place to discuss these
low-level details is Squid Bugzilla. I suggest that you open a new bug
report there. If you
Hi,Alex
thank you for your reply
Sorry for my English，First of all，
> I am not sure whether "it" in your sentence refers to gdb or Squid, but
> if Squid dereferences an unaligned data field in shared memory, then it
> is most likely a Squid bug.
"it" is refers to Squid.
i want to Explain my prob
Context: hindsight1 was replying to a 2016 email archived at
http://lists.squid-cache.org/pipermail/squid-users/2016-October/012881.html
On 11/10/19 7:13 AM, hindsight1 wrote:
> When running Squid4.8 on the arm using SMP. And setting 4 or 7,9 worker
> ,the same error occurred in the log.
>>> Re
Hi,Alex
When running Squid4.8 on the arm using SMP. And setting 4 or 7,9 worker
,the same error occurred in the log.
>> Received Bus Error...dying,
Debugging the core file with gdb found that the address was not aligned.
Does it consider the case where only address-aligned access is supported
On Mon, 2016-10-03 at 11:33 -0600, Alex Rousskov wrote:
On 10/03/2016 04:50 AM, Jasper Van Der Westhuizen wrote:
This morning I had some problems with some of our proxies. 2 Proxies in
cluster A crashed with the below errors. The shortly afterwards 4 in
cluster B did the same. Both clusters ar
On 10/03/2016 04:50 AM, Jasper Van Der Westhuizen wrote:
> This morning I had some problems with some of our proxies. 2 Proxies in
> cluster A crashed with the below errors. The shortly afterwards 4 in
> cluster B did the same. Both clusters are configured to run their cache
> in memory with SMP an
Hi all
This morning I had some problems with some of our proxies. 2 Proxies in cluster
A crashed with the below errors. The shortly afterwards 4 in cluster B did the
same. Both clusters are configured to run their cache in memory with SMP and 4
workers configured.
2016/10/03 10:28:37 kid3| snm
