|
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:
-- 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. |
- [Machinekit] Debian package related problem cern
- Re: [Machinekit] Debian package related problem [email protected]
- Re: [Machinekit] Debian package related problem [email protected]
- Re: [Machinekit] Debian package related prob... [email protected]
- [Machinekit] Re: Debian package related problem cern
