Board index FlightGear Development New features

FGPython an propose for Python as an nasal alternative

Discussion and requests for new features. Please note that FlightGear developers are volunteers and may or may not be able to consider these requests.

Re: FGPython an propose for Python as an nasal alternative

Postby www2 » Thu Oct 20, 2016 4:11 pm

thx Edward.
I have no nothing chance with my python install and the libs are locate: /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/libpython3.5.so or /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/libpython3.5m.so on ubuntu 16.04 64bit

Jean-Paul Anceaux

here is a backtrace with debug symbols
Code: Select all
#0  0x00007ffff1fcc418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1  0x00007ffff1fce01a in __GI_abort () at abort.c:89
#2  0x00007ffff200e72a in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff2125c7f "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
#3  0x00007ffff20af89c in __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7ffff2125c61 "stack smashing detected") at fortify_fail.c:37
#4  0x00007ffff20af840 in __stack_chk_fail () at stack_chk_fail.c:28
#5  0x000000000188279a in Props_tp_init (self=0x7fffe44a3710, args=0x7fffe44f4048, keywords=0x7fffdf8d1ec8) at /home/jean-paul/fgfs2/flightgear/src/Python/prop_tree.cxx:1525
#6  0x00007ffff3d2f276 in ?? () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#7  0x00007ffff3e258ee in PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#8  0x00007ffff3e607ff in PyEval_EvalFrameEx () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#9  0x00007ffff3ef6c0c in ?? () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#10 0x00007ffff3ef6ce3 in PyEval_EvalCodeEx () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#11 0x00007ffff3e5e89b in PyEval_EvalCode () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#12 0x00007ffff3e7bd3f in PyRun_StringFlags () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#13 0x00007ffff3e7cd7b in PyRun_SimpleStringFlags () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
#14 0x000000000187ccd3 in FGPythonSys::init (this=0x1e90e470) at /home/jean-paul/fgfs2/flightgear/src/Python/PythonSys.cxx:95
#15 0x00000000013ec409 in fgPostInitSubsystems () at /home/jean-paul/fgfs2/flightgear/src/Main/fg_init.cxx:917
#16 0x000000000140fbb3 in fgIdleFunction () at /home/jean-paul/fgfs2/flightgear/src/Main/main.cxx:350
#17 0x0000000001b97470 in fgOSMainLoop () at /home/jean-paul/fgfs2/flightgear/src/Viewer/fg_os_osgviewer.cxx:334
#18 0x00000000014107b8 in fgMainInit (argc=2, argv=0x7fffffffcc88) at /home/jean-paul/fgfs2/flightgear/src/Main/main.cxx:544
#19 0x00000000013dcc86 in main (argc=2, argv=0x7fffffffcc88) at /home/jean-paul/fgfs2/flightgear/src/Main/bootstrap.cxx:244


edit:
when i remove this line (/home/jean-paul/fgfs2/flightgear/src/Python/PythonSys.cxx:95)
Code: Select all
PyRun_SimpleString("builtins.props = prop_tree.Props(new_tree=False)");

than crash fgfs here: /home/jean-paul/fgfs2/flightgear/src/Python/PythonSys.cxx:111

edit two:
I have narrow it down to
Code: Select all
prop_tree.Props(new_tree=False)


edit three:
After chance the code from
Code: Select all
prop_tree.Props(new_tree=False)
to
Code: Select all
prop_tree.Props()
flight gear don't crash.
www2
 
Posts: 254
Joined: Thu Apr 16, 2009 1:58 pm

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Sat Oct 22, 2016 6:17 pm

This is quite bizarre and makes no sense. The code for this Props.__init__() function is:

Code: Select all
// The Props.__init__() type method.
static int Props_tp_init(Props *self, PyObject *args, PyObject *keywords) {
    // Python object declarations.
    bool new_tree=true;

    // Keyword list.
    static char *keyword_list[] = {
        (char *)"new_tree",
        NULL
    };

    // Parse the function arguments.
    if (!PyArg_ParseTupleAndKeywords(args, keywords, "|p", keyword_list, &new_tree))
        return -1;

    // Create an empty property tree.
    if (new_tree) {
        self->_props = new SGPropertyNode;
    }
    self->_new_tree = new_tree;

    // Success.
    return 0;
}


The "|p" argument will convert the Python bool into a C bool (0 or 1). What if you run:

Code: Select all
    prop_tree.Props(new_tree=True)


Regards,
Edward
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Sat Oct 22, 2016 7:35 pm

Do you also have CppUnit compiled? Can you run the full test suite with:

Code: Select all
$ make test_suite

Cheers,
Edward
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby www2 » Sat Oct 22, 2016 9:58 pm

Done:
Code: Select all
$ make test_suite
[ 34%] Built target JSBSim
[ 37%] Built target fgsqlite3
[ 62%] Built target iaxclient_lib
[ 78%] Built target flite_hts
[ 81%] Built target hts_engine
[ 81%] Automatic moc for target fglauncher
[ 81%] Built target fglauncher_automoc
[ 90%] Built target fglauncher
Scanning dependencies of target run_test_suite
[ 90%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/gui_tests/fgGuiTestRunner.cxx.o
[ 90%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/simgear_tests/math/TestSuite.cxx.o
[ 90%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/simgear_tests/math/test-up.cxx.o
[ 90%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/simgear_tests/props/TestSuite.cxx.o
[ 90%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/simgear_tests/props/test_props.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/simgear_tests/fgSimgearTestRunner.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/system_tests/fgSystemTestRunner.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/general/TestSuite.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/general/test-mktime.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/Python/TestSuite.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/Python/test_prop_tree.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/__/src/Python/PythonSys.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/__/src/Python/fg_sys.cxx.o
[ 93%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/__/src/Python/prop_tree.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/Scripting/TestSuite.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/Scripting/testNasalSys.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/unit_tests/fgUnitTestRunner.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/formatting.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/fgCompilerOutputter.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/fgTestListener.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/logging.cxx.o
[ 96%] Building CXX object test_suite/CMakeFiles/run_test_suite.dir/testSuite.cxx.o
[100%] Linking CXX executable run_test_suite
[100%] Built target run_test_suite
[100%] Running the full FlightGear test-suite.


################
# System tests #
################


----------------------------------------------------------------------
Ran 0 tests in 1e-06 seconds.

[ OK ]



##############
# Unit tests #
##############

.*** stack smashing detected ***: ./run_test_suite terminated
Aborted (core dumped)
test_suite/CMakeFiles/test_suite.dir/build.make:57: recept voor doel 'test_suite/CMakeFiles/test_suite' is mislukt
make[3]: *** [test_suite/CMakeFiles/test_suite] Fout 134
CMakeFiles/Makefile2:1970: recept voor doel 'test_suite/CMakeFiles/test_suite.dir/all' is mislukt
make[2]: *** [test_suite/CMakeFiles/test_suite.dir/all] Fout 2
CMakeFiles/Makefile2:1977: recept voor doel 'test_suite/CMakeFiles/test_suite.dir/rule' is mislukt
make[1]: *** [test_suite/CMakeFiles/test_suite.dir/rule] Fout 2
Makefile:524: recept voor doel 'test_suite' is mislukt
www2
 
Posts: 254
Joined: Thu Apr 16, 2009 1:58 pm

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Sun Oct 23, 2016 10:29 am

Is that Flemish? This is what I see, after pre-compiling:

Code: Select all
$ make -j 3 test_suite
[  3%] Built target fgsqlite3
[ 11%] Built target iaxclient_lib
[ 14%] Built target hts_engine
[ 37%] [ 37%] Built target flite_hts
Automatic moc for target fglauncher
[ 37%] Built target fglauncher_automoc
[ 77%] Built target JSBSim
[ 88%] Built target fglauncher
[100%] Built target run_test_suite
[100%] Running the full FlightGear test-suite.


################
# System tests #
################


----------------------------------------------------------------------
Ran 0 tests in 2e-06 seconds.

[ OK ]



##############
# Unit tests #
##############

...................................................................................................................................................................................................................................................F.
======================================================================
FAIL: PropTreeTestCase::testFailure
----------------------------------------------------------------------
Assertion: test_prop_tree.cxx:895:
assertion failed
- Expression: PyRun_SimpleString("print(props.does_not_exist)") == 0

----------------------------------------------------------------------
# SG_LOG, SG_ALL class, SG_BULK priority

python:2:/flightgear/src/flightgear-flightgear/src/Python/PythonSys.cxx:39: Creation.
python:2:/flightgear/src/flightgear-flightgear/src/Python/PythonSys.cxx:87: Initialisation.
general:1:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:889: Log bulk test
general:2:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:890: Log debug test
general:3:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:891: Log info test
general:4:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:892: Log warn test
general:5:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:893: Log alert test
python:3:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36: This is a test designed to fail
python:2:/flightgear/src/flightgear-flightgear/src/Python/prop_tree.cxx:831: Deleting the Python interface to '/does-not-exist'.
python:5:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36: Traceback (most recent call last):
python:5:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36:   File "<string>", line 1, in <module>
python:5:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36: AttributeError: The property tree node '/does-not-exist' does not exist.
python:2:/flightgear/src/flightgear-flightgear/src/Python/PythonSys.cxx:66: Destruction.

----------------------------------------------------------------------
# SG_LOG, SG_ALL class, SG_BULK only priority

general:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:889: Log bulk test

----------------------------------------------------------------------
# SG_LOG, SG_ALL class, SG_DEBUG only priority

python:/flightgear/src/flightgear-flightgear/src/Python/PythonSys.cxx:39: Creation.
python:/flightgear/src/flightgear-flightgear/src/Python/PythonSys.cxx:87: Initialisation.
general:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:890: Log debug test
python:/flightgear/src/flightgear-flightgear/src/Python/prop_tree.cxx:831: Deleting the Python interface to '/does-not-exist'.
python:/flightgear/src/flightgear-flightgear/src/Python/PythonSys.cxx:66: Destruction.

----------------------------------------------------------------------
# SG_LOG, SG_ALL class, SG_INFO only priority

general:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:891: Log info test
python:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36: This is a test designed to fail

----------------------------------------------------------------------
# SG_LOG, SG_ALL class, SG_WARN only priority

general:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:892: Log warn test

----------------------------------------------------------------------
# SG_LOG, SG_ALL class, SG_ALERT only priority

general:/flightgear/src/flightgear-flightgear/test_suite/unit_tests/Python/test_prop_tree.cxx:893: Log alert test
python:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36: Traceback (most recent call last):
python:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36:   File "<string>", line 1, in <module>
python:/flightgear/src/flightgear-flightgear/src/Python/fg_sys.cxx:36: AttributeError: The property tree node '/does-not-exist' does not exist.

----------------------------------------------------------------------
# STDOUT and STDERR

Log std::cout test
Log std::cerr test

----------------------------------------------------------------------
Ran 245 tests in 0.35 seconds.

Failures = 1
Errors   = 0

[ FAILED ]



#############
# GUI tests #
#############


----------------------------------------------------------------------
Ran 0 tests in 1e-06 seconds.

[ OK ]



######################
# Simgear unit tests #
######################

..
----------------------------------------------------------------------
Ran 2 tests in 0.35 seconds.

[ OK ]



########################################
# Summary of the FlightGear test suite #
########################################


Synopsis
========

System/functional tests ....................................... [ OK ]
Unit tests ................................................ [ Failed ]
GUI tests ..................................................... [ OK ]
Simgear unit tests ............................................ [ OK ]
Synopsis .................................................. [ Failed ]


test_suite/CMakeFiles/test_suite.dir/build.make:49: recipe for target 'test_suite/CMakeFiles/test_suite' failed
make[3]: *** [test_suite/CMakeFiles/test_suite] Error 1
CMakeFiles/Makefile2:1720: recipe for target 'test_suite/CMakeFiles/test_suite.dir/all' failed
make[2]: *** [test_suite/CMakeFiles/test_suite.dir/all] Error 2
CMakeFiles/Makefile2:1728: recipe for target 'test_suite/CMakeFiles/test_suite.dir/rule' failed
make[1]: *** [test_suite/CMakeFiles/test_suite.dir/rule] Error 2
Makefile:470: recipe for target 'test_suite' failed
make: *** [test_suite] Error 2
[edward@localhost build_python (python/r9)]$
  BRANCH: python/r9  (85feb8d) / 7 uncommitted changes / STASHES: 2                                                                                                                                               
$


The single failure is deliberate. If you have a look, you'll see that there is now a "test_suite/run_test_suite" binary file (in other OSes, it might be in a "test_suite" subdirectory). Could you run this through "gdb" to work out where the "stack smashing" occurred? E.g.:

Code: Select all
$ gdb test_suite/run_test_suite
GNU gdb (GDB) 7.8.1-7.mga5 (Mageia release 5)
[snip]
(gdb) run
[snip]
(gdb) bt


Maybe I have a bug that works with my gcc version (4.9.2) and python version (3.4.3), but is problematic in your versions.

Cheers,
Edward

Edit: Running the "run_test_suite" binary through valgrind is also very informative, however note that the initialisation and destruction of Python itself leads to a lot of memory leak messages (likely false positives), so hunting down issues in FGPythonSys is challenging.
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Sun Oct 23, 2016 12:16 pm

Hi Jean-Paul,

I have just managed to use a self-compiled version of Python (3.5.2) and FGPythonSys runs perfectly fine with this version. So there must be something strange with your Python or gcc version triggering this issue. But just because I don't see it, it might still be an issue. I'll have to hunt this down with Valgrind.

Cheers,
Edward
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Sun Oct 23, 2016 12:25 pm

For the record, here is how I use Valgrind with FGPythonSys, with a self-compiled version of Python.

Python

Firstly look at "Misc/README.valgrind":

This document describes some caveats about the use of Valgrind with
Python. Valgrind is used periodically by Python developers to try
to ensure there are no memory leaks or invalid memory reads/writes.

If you don't want to read about the details of using Valgrind, there
are still two things you must do to suppress the warnings. First,
you must use a suppressions file. One is supplied in
Misc/valgrind-python.supp. Second, you must do one of the following:

* Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c,
then rebuild Python
* Uncomment the lines in Misc/valgrind-python.supp that
suppress the warnings for PyObject_Free and PyObject_Realloc

If you want to use Valgrind more effectively and catch even more
memory leaks, you will need to configure python --without-pymalloc.
PyMalloc allocates a few blocks in big chunks and most object
allocations don't call malloc, they use chunks doled about by PyMalloc
from the big blocks. This means Valgrind can't detect
many allocations (and frees), except for those that are forwarded
to the system malloc. Note: configuring python --without-pymalloc
makes Python run much slower, especially when running under Valgrind.
You may need to run the tests in batches under Valgrind to keep
the memory usage down to allow the tests to complete. It seems to take
about 5 times longer to run --without-pymalloc.
[snip]


So after uncommenting both Py_USING_MEMORY_DEBUGGER and the PyObject_Free and PyObject_Realloc suppressions, I then compile and install using:

Code: Select all
[edward@localhost Python-3.5.2]$ cat .configure_valgrind
./configure --prefix=/data/python/ --with-valgrind --without-pymalloc --enable-shared
[edward@localhost Python-3.5.2]$ ./.configure
[snip]
[edward@localhost Python-3.5.2]$ make -j 3 install


This places my custom Python version into /data/python/.

FGPythonSys

Simgear is compiled as normal, e.g.:

Code: Select all
[edward@localhost build_python (python/r6)]$
  BRANCH: python/r6  (8714cff) / 1 uncommitted change / STASHES: 1
$ cat .cmake
cmake .. -DENABLE_RTI=ON -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/flightgear
[edward@localhost build_python (python/r6)]$
  BRANCH: python/r6  (8714cff) / 1 uncommitted change / STASHES: 1
$ ./.cmake
[snip]
[edward@localhost build_python (python/r6)]$
  BRANCH: python/r6  (8714cff) / 1 uncommitted change / STASHES: 1
$ make -j 3 install


But for FlightGear, I use:

Code: Select all
[edward@localhost build_python (python/r9)]$
  BRANCH: python/r9  (85feb8d) / 8 uncommitted changes / STASHES: 2
$ cat .cmake_py3.5
cmake .. -DENABLE_RTI=ON -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/flightgear -DPYTHON_LIBRARY=/data/python/lib/libpython3.5m.so -DPYTHON_INCLUDE_DIR=/data/python/include/python3.5m/ -DCMAKE_CXX_FLAGS="-ldl -lpthread"
[edward@localhost build_python (python/r9)]$
  BRANCH: python/r9  (85feb8d) / 8 uncommitted changes / STASHES: 2
$ ./.cmake_py3.5
[snip]
$ make -j 3 test_suite


Then to run this with valgrind:

Code: Select all
[edward@localhost build_python (python/r9)]$
  BRANCH: python/r9  (85feb8d) / 8 uncommitted changes / STASHES: 2
$ cat .valgrind
valgrind --leak-check=full --track-origins=yes --suppressions=/data/python/src/Python-3.5.2/Misc/valgrind-python.supp test_suite/run_test_suite
[edward@localhost build_python (python/r9)]$
  BRANCH: python/r9  (85feb8d) / 8 uncommitted changes / STASHES: 2
$ ./.valgrind 2&> valgrind.log


Regards,
Edward
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby www2 » Mon Oct 24, 2016 12:55 am

Edwards i have reinstall my ubuntu install and just found that the problem is a stack smash. i don't know with function is the problem, yet.
www2
 
Posts: 254
Joined: Thu Apr 16, 2009 1:58 pm

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Mon Oct 24, 2016 6:15 am

Which Python 3.5 version is this? Could you try downloading the latest 3.5.2 and compiling it yourself (as above)? I wonder if it is a bug in an early Python 3.5 version. I don't see this with Python 3.4.3 or 3.5.2 on Linux. And I don't see this on Windows.

Regards,
Edward


P.S. Using Valgrind on the test suite, you'll see that there is an issue with aliasing in the property tree. This is not the problem here though - it is an issue with the FG property tree destruction not calling the unalias() props function.
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby www2 » Mon Oct 24, 2016 7:33 am

Edward I have a strange feeling that this is not a python bug if the code of fgpython is not chance between r6/r7 and r9

Edit: i have add the line that shows the version number that shows that i use python 3.5.2 and the code compleert the Props_tp_init function in prop_tree.cxx
Last edited by www2 on Mon Oct 24, 2016 8:09 am, edited 1 time in total.
www2
 
Posts: 254
Joined: Thu Apr 16, 2009 1:58 pm

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Mon Oct 24, 2016 7:39 am

Did your Python version change between python/r6 and python/r9 of my flightgear fork? Maybe I'll try a Ubuntu 16.04 install in a VM later to see what is so strange with this.

Regards,
Edward

Edit: Does the python/r5 branch work?
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby www2 » Mon Oct 24, 2016 8:11 am

if i remember r5 works.

And what i say in a early edit:
i have add the line that shows the version number that shows that i use python 3.5.2 and the code compleert the Props_tp_init function in prop_tree.cxx
www2
 
Posts: 254
Joined: Thu Apr 16, 2009 1:58 pm

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Mon Oct 24, 2016 9:13 am

I just compiled and tested both Python 3.5.0 and 3.5.1 and they work without problem. Now I have to download Ubuntu 16.04 and test that.

Regards,
Edward
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

Re: FGPython an propose for Python as an nasal alternative

Postby www2 » Mon Oct 24, 2016 9:34 am

First thing i experted that i F*ck up my system.
For testing i use download_and_compile.sh for building fgfs.
www2
 
Posts: 254
Joined: Thu Apr 16, 2009 1:58 pm

Re: FGPython an propose for Python as an nasal alternative

Postby bugman » Mon Oct 24, 2016 11:50 am

I can confirm that it is a Ubuntu 16.04 only issue. I see the "stack smashing" issue in the test suite in a newly installed VM. Now to work out why.

Regards,
Edward
bugman
Moderator
 
Posts: 1679
Joined: Thu Mar 19, 2015 9:01 am
Version: next

PreviousNext

Return to New features

Who is online

Users browsing this forum: No registered users and 2 guests