actisense-serial on armhf (raspbian jessie) about canboat

[keesverruijt]

Compile with debug mode, then examine the core dump in gdb.

[jlaba]

I figured out how to create core dump files and with my very little knowledge of gdb I tried to find out the segfault reason.

In case of

• n2kd it seems to be an issue in pgnIdx in _start
• analyzer pgnList in _start
• actistense_serial ?

I have attached the core dump files for those programs [core-dumps.ZIP](https://github.com/canboat/canboat/files/951766/core-dumps.ZIP.

Interestingly, the segfault does not appear, if I compile canboat on raspbian itself. Compiling it on debian armhf leads to this segfaults. I don't observed this by other packages.

Do you have an Idea, what the problem might be?

[keesverruijt]

I’m very sympathetic, but as you realise probably it is very hard for someone who doesn’t have your hardware to reproduce this. The fact that you need a cross deploy to trigger the bug indicates something is not alike between the 2 systems. A core dump in _start seems to indicate that there is an incompatibility between the dynamic libraries of the 2 systems. If it really crashes in _start, it means the canboat code hasn’t even run yet.

…

On 24 Apr 2017, at 15:00, jlaba ***@***.***> wrote: I figured out how to create core dump files and with my very little knowledge of gdb I tried to find out the segfault reason. In case of n2kd it seems to be an issue in pgnIdx in _start analyzer pgnList in _start actistense_serial ? I have attached the core dump files for those programs. Interestingly, the segfault does not appear, if I compile canboat on raspbian itself. Compiling it on debian armhf leads to this segfaults. I don't observed this by other packages. Do you have an Idea, what the problem might be? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABiJeka9KmqVtrOt1rYP8qKi49PPxm5uks5rzJzygaJpZM4NFcUJ>.

[jlaba]

Thanks for your reply. I awaited such a bad situation. I created an raspbian package to bypass it. The package could be found in http://ftp.engsas.de/unstable/gnuboat-raspbian/ repository.