If you are up for it, you can try to debug the core dump that you have

http://www.machinekit.io/docs/code/Debugging-RT-components/

I have found that this works quite well on rt-preempt kernels, in pinpointing exactly what triggered a segfault.

The log you originally posted shows the error report, but it is far from certain exactly where this is
occurring, because motion continues to create pins either side of it.


On 23/11/18 16:09, [email protected] wrote:

On 23/11/18 16:05, [email protected] wrote:


I am not disputing that. Given that it started with "Merge pull request #1409 from ArcEye/remove-hard-kernel-threads" I would guess that it is specific to i386 platform. And I guess that nobody else is using the old i386 or if they are they are not upgrading it. But I will try it on other i386 PC to be sure.

No, they relate to rtai kernels and hard threaded Xenomai kernels

We have not built for these for a long time, this just removed references to them from the Makefiles

i386 is still built for, albeit you are right, there cannot be many still around, nearly all PC processors no matter how
humble have been 64 bit for quite a long time.




--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to