Segfault at src/lib/misc.c:1193 in 3.0.4 (3.0.11 looks very similar)

[Mike Ely]

On 10/03/2016 12:30 PM, Alan DeKok wrote:
>   Well.. the code already checks that the array entries are non-NULL.  So the array is fine when the server starts.
>
>   If it's NULL later, then something else is going on.  Maybe there's an unrelated error which smashes the array entry.
>
>   But as I said, I've never seen this.  The unusual (but possible) reason could be that you have a problem with the system RAM.  i.e. it's failing.
>
>   I've seen that before.
>

Maybe an arch problem? We get the same problem on both hosts (a/b 
configuration) so it's unlikely they both have failed sticks of RAM.

They are running with Atom D525 processors. Here's /proc/cpuinfo (2 
sockets, total 4 cores):

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 28
model name      : Intel(R) Atom(TM) CPU D525   @ 1.80GHz
stepping        : 10
microcode       : 0x107
cpu MHz         : 1795.613
cache size      : 512 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm movbe 
lahf_lm dtherm
bogomips        : 3591.22
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management: