On Sat, Dec 07, 2019 at 09:31:20AM +0100, Florian Obser wrote: > 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?
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 0x00000000 in ?? () > > 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 > > Since frontend and engine are reporting in, it's the main process > aborting. I can't spot it from code inspection. I quickly tried to reproduce by manually unplug/replug power, but I can't achieve to get the same result. Currently, I am seeing it when I am switching installation power source using a transfer switch[1] from/to engine-generator[2]. As I am feeling unconfortable with such vocabulary, I linked some terms I used to wikipedia: [1] https://en.wikipedia.org/wiki/Transfer_switch [2] https://en.wikipedia.org/wiki/Engine-generator 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... Thanks. -- Sebastien Marie
