Debugging/ru: Difference between revisions
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
Line 23: | Line 23: | ||
Enter the following in your terminal window: |
Enter the following in your terminal window: |
||
<pre> |
<pre> |
||
cd FreeCAD/bin |
|||
gdb FreeCAD |
|||
handle SIG33 noprint nostop |
|||
run |
|||
</pre> |
</pre> |
||
FreeCAD will now start up. Perform the steps that cause FreeCAD to crash, then enter 'bt' in your terminal window. This will generate a lengthy listing of exactly what the program was doing when it crash. Include this with your problem report. |
FreeCAD will now start up. Perform the steps that cause FreeCAD to crash, then enter 'bt' in your terminal window. This will generate a lengthy listing of exactly what the program was doing when it crash. Include this with your problem report. |
Revision as of 20:50, 8 November 2014
Певые испытания
Перед тем как пройти через боль от процесса отладки , используйте набор для тестирования(тестовый модуль), чтобы проверить будут ли работать стандартные тесты должным образом. Если нет, то возможно дело, поломанной(нарушенной) установке.
командная строка
Отладка FreeCAD поддерживает несколько внутренних механизмов. Версия FreeCAD без графического режима предоставляет варианты поддержки отладки:
- -v
- С "v" опцией FreeCAD дает более подробный вывод
- -l
- С "l" опцией FreeCAD записывает дополнительную информацию в лог-файл.
Generating a Backtrace
If you are running a version of FreeCAD from the bleeding edge of the development curve, it may "crash". You can help solve such problems by providing the developers with a "backtrace". To do this, you need to be running a "debug build" of the software. "Debug build" is a parameter that is set at compile time, so you'll either need to compile FreeCAD yourself, or obtain a pre-compiled "debug" version.
For Linux
Prerequisites:
- software package gdb installed
- a debug build of FreeCAD
- a FreeCAD model that causes a crash
Steps: Enter the following in your terminal window:
cd FreeCAD/bin gdb FreeCAD handle SIG33 noprint nostop run
FreeCAD will now start up. Perform the steps that cause FreeCAD to crash, then enter 'bt' in your terminal window. This will generate a lengthy listing of exactly what the program was doing when it crash. Include this with your problem report.
Python debugging
Here is an example of using winpdb inside FreeCAD:
- Run winpdb and set the password (e.g. test)
- Create a Python file with this content
import rpdb2
rpdb2.start_embedded_debugger("test")
import FreeCAD
import Part
import Draft
print "hello"
print "hello"
import Draft
points=[FreeCAD.Vector(-3.0,-1.0,0.0),FreeCAD.Vector(-2.0,0.0,0.0)]
Draft.makeWire(points,closed=False,face=False,support=None)
- Start FreeCAD and load the above file into FreeCAD
- Press F6 to execute it
- Now FreeCAD will become unresponsive because the Python debugger is waiting
- Switch to the Windpdb GUI and click on "Attach". After a few seconds an item "<Input>" appears where you have to double-click
- Now the currently executed script appears in Winpdb.
- Set a break at the last line and press F5
- Now press F7 to step into the Python code of Draft.makeWire