On Sun, Dec 15, 2019 at 12:02:15AM -0700, Theo de Raadt wrote:
> Or even better, via the typical macro expansion used for this type of
> union, it should use ifr_addr
>
nice one, OK florian@
> Index: slaacd.c
> ===
> RCS file:
On Sun, Dec 15, 2019 at 12:02:15AM -0700, Theo de Raadt wrote:
> >
> > It should use the specific element in the union, so this might be the
> > fix.
> >
>
> Or even better, via the typical macro expansion used for this type of
> union, it should use ifr_addr
ok semarie@
> Index: slaacd.c
>
Theo de Raadt wrote:
> Sebastien Marie wrote:
>
> > On Sat, Dec 07, 2019 at 11:47:58AM +0100, Sebastien Marie wrote:
> > >
> > > For now, I recompiled slaacd with debug symbols, and will keep it running
> > > like
> > > that in order to catch it the next time. But such switchs aren't very
>
Sebastien Marie wrote:
> On Sat, Dec 07, 2019 at 11:47:58AM +0100, Sebastien Marie wrote:
> >
> > For now, I recompiled slaacd with debug symbols, and will keep it running
> > like
> > that in order to catch it the next time. But such switchs aren't very
> > frequent...
>
> A new one, with
On Sat, Dec 07, 2019 at 11:47:58AM +0100, Sebastien Marie wrote:
>
> For now, I recompiled slaacd with debug symbols, and will keep it running like
> that in order to catch it the next time. But such switchs aren't very
> frequent...
A new one, with symbols this time. I still saw it only i386
which one it is? Does this leave a core file
> behind?
I have a /slaacd.core , but the backtrace seems really useless...
Program terminated with signal 6, Aborted.
#0 0x156cda8b in ?? ()
(gdb) bt
#0 0x156cda8b in ?? ()
#1 0x156cce20 in ?? ()
#2 0x0000 in ?? ()
> > Dec 7 06:45:42
On Sat, Dec 07, 2019 at 07:09:17AM +0100, Sebastien Marie wrote:
> Hi,
>
> On an i386 and an aarch64 hosts, I have occasionally the following error in
> syslog:
is there a way to tell which one it is? Does this leave a core file
behind?
>
> Dec 7 06:45:42 joe slaacd: backwar
Hi,
On an i386 and an aarch64 hosts, I have occasionally the following error in
syslog:
Dec 7 06:45:42 joe slaacd: backwards memcpy
Dec 7 06:45:43 joe slaacd[98303]: frontend exiting
Dec 7 06:45:43 joe slaacd[76753]: engine exiting
and slaacd daemon died.
It occurs on short power outage
