Debugging source code of LinuxCNC - possible?
- zz912
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 509
- Thank you received: 81
02 Jun 2023 18:43 #272761
by zz912
Debugging source code of LinuxCNC - possible? was created by zz912
Attachments:
Please Log in or Create an account to join the conversation.
- spumco
- Offline
- Platinum Member
Less
More
- Posts: 1829
- Thank you received: 738
02 Jun 2023 18:55 #272764
by spumco
Replied by spumco on topic Debugging source code of LinuxCNC - possible?
VS code runs on Linux. That's what I use for HAL and gcode editing. There's even a nice hal-file plugin available.
Or maybe I misunderstood your question?
Or maybe I misunderstood your question?
Please Log in or Create an account to join the conversation.
- zz912
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 509
- Thank you received: 81
04 Jun 2023 17:49 #272892
by zz912
I found bug. github.com/LinuxCNC/linuxcnc/issues/2453...uecomment-1570683157
Python is causing me the most trouble.
I have "parameter":I think it works wrong.
I don't know what's driving it.
I know, that is come from:But the file linuxcnc.py does not exist.
I'm looking for a way to find out how some parts of the code work. At the moment, I mainly read the code and verify its functionality by writing appropriate information to the console using the print function.
If I could open LCNC in Microsoft's Visul Studio, I could see step by step how the code is read.
I'm not insisting on using Microsoft's Visul Studio, but anything better than randomly browsing through files.
I wonder if there is a more efficient way of working.
Replied by zz912 on topic Debugging source code of LinuxCNC - possible?
I am trying to understand how LCNC source code works.Or maybe I misunderstood your question?
I found bug. github.com/LinuxCNC/linuxcnc/issues/2453...uecomment-1570683157
Python is causing me the most trouble.
I have "parameter":
self.stat.task_mode
I don't know what's driving it.
I know, that is come from:
import linuxcnc
I'm looking for a way to find out how some parts of the code work. At the moment, I mainly read the code and verify its functionality by writing appropriate information to the console using the print function.
If I could open LCNC in Microsoft's Visul Studio, I could see step by step how the code is read.
I'm not insisting on using Microsoft's Visul Studio, but anything better than randomly browsing through files.
I wonder if there is a more efficient way of working.
Please Log in or Create an account to join the conversation.
- Aciera
- Offline
- Administrator
Less
More
- Posts: 4001
- Thank you received: 1729
04 Jun 2023 19:02 - 04 Jun 2023 19:03 #272900
by Aciera
Replied by Aciera on topic Debugging source code of LinuxCNC - possible?
I really don't know either but I think that what you are looking for might actually be some C++ library that is callable from python through python-boost or something.
Last edit: 04 Jun 2023 19:03 by Aciera.
The following user(s) said Thank You: zz912
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5706
- Thank you received: 2084
05 Jun 2023 00:42 #272919
by phillc54
Replied by phillc54 on topic Debugging source code of LinuxCNC - possible?
possibly hard to find because of the 'emc' name:
github.com/LinuxCNC/linuxcnc/blob/master...ensions/emcmodule.cc
github.com/LinuxCNC/linuxcnc/blob/master...ensions/emcmodule.cc
The following user(s) said Thank You: zz912
Please Log in or Create an account to join the conversation.
- zz912
- Topic Author
- Offline
- Platinum Member
Less
More
- Posts: 509
- Thank you received: 81
12 Jun 2023 06:08 #273369
by zz912
Replied by zz912 on topic Debugging source code of LinuxCNC - possible?
I would like to ask why the emcmodule.cc file is in "/axis/" folder?
I would look for such a file in the "/python_interface/" folder.
Is this a historical reason?
I would look for such a file in the "/python_interface/" folder.
Is this a historical reason?
Please Log in or Create an account to join the conversation.
Time to create page: 0.135 seconds