Hi Philippe,
do you have any other conclusion from your investigation?
Ondrej
--
Ondřej Surý
ond...@sury.org
> On 21 Nov 2018, at 23:47, Philippe Duke wrote:
>
> (gdb)
> #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> set = {__val = {16387, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 281473428432960, 281473462095732, 28147346372, 281473428443584,
> 281473428432960,
> 281473462095632}}
> pid =
> tid =
> #1 0xa5b8cdf4 in __GI_abort () at abort.c:89
> save_stage = 2
> act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction =
> 0x0}, sa_mask = {__val = {0 }}, sa_flags = 0,
> sa_restorer = 0x0}
> sigs = {__val = {32, 0 }}
> #2 0xa5bc4628 in __libc_message (do_abort=do_abort@entry=2,
> fmt=fmt@entry=0xa5c79f20 "*** %s ***: %s terminated\n")
> at ../sysdeps/posix/libc_fatal.c:175
> ap = {__stack = 0xa3b72c10, __gr_top = 0xa3b72c10,
> __vr_top = 0xa3b72be0, __gr_offs = -32, __vr_offs = -128}
> fd = 2
> on_2 =
> list =
> nlist =
> cp =
> written =
> #3 0xa5c33398 in __GI___fortify_fail
> (msg=msg@entry=0xa5c79f08 "stack smashing detected") at
> fortify_fail.c:30
> No locals.
> #4 0xa5c3334c in __stack_chk_fail () at stack_chk_fail.c:28
> No locals.
> #5 0xa6481c48 in dns_rdataset_additionaldata
> (rdataset=0x9bbb8b70, add=0xbd7ff648 ,
> arg=0xa3b72d38)
> at ../../../lib/dns/rdataset.c:642
> rdata = {data = 0xa3b72ec0 "", length = 0, rdclass = 0, type
> = 0, flags = 0, link = {prev = 0x0, next = 0x0}}
> result =
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>
>
> Another one. Looking up for hardware issue. Recompling with ARM errata
> mitigations. But this is really weird anyway.
>
> --
> Philippe Duke
> Network software engineer
> System-level developer
>
> NetAssist LLC
> Ukraine
> Khreshchatyk Street, 10B, office 8
> AS29632
>
> http://netassist.ua
> Our GitHub Repository:
> https://github.com/netassist-ua
>
