Stackless 3.4 debug build testsuite failures

Originally reported by: Anselm Kruis (Bitbucket: akruis, GitHub: akruis)

---

Compile a version from branch 3.4-slp on amd64 Linux (Debian 7.8):

$ ./configure --prefix=/tmp/slp342 --with-pydebug
$ make

Then run the test suite

$ make test

Several test cases that pass with C-Python fail:

[140/389/2] test_threading
test test_threading failed -- Traceback (most recent call last):
  File "/home/anselm/src/stackless2/Lib/test/test_threading.py", line 538, in test_main_thread_after_fork_from_nonmain_thread
    self.assertEqual(err, b"")
AssertionError: b"python: Stackless/module/taskletobject.c[163 chars]st):" != b''

[166/389/3] test_tracemalloc
test test_tracemalloc failed -- Traceback (most recent call last):
  File "/home/anselm/src/stackless2/Lib/test/test_tracemalloc.py", line 188, in test_get_traced_memory
    self.assertLessEqual(peak_size - size, max_error)
AssertionError: 137788 not less than or equal to 2048

[366/389/4] test_concurrent_futures
Fatal Python error: Fatal Python error: Fatal Python error: Segmentation fault

[389/389/4] test_multiprocessing_fork
Fatal Python error: Segmentation fault

Here test.regrtest hangs.

About the segfault. If you disable the new faulthandler and undef PY_LOCAL_AGGRESSIVE in ceval.c you can get a useful core dump.
The crash is caused by a cframe that is used as argument for PyEval_EvalFrame_value.
That is a serious bug.

disable_faulthandler.patch.zip

---

• Bitbucket: https://bitbucket.org/stackless-dev/stackless/issue/75

Original comment by Anselm Kruis (Bitbucket: akruis, GitHub: akruis):

---

Patch used to enable usable core files. Of course you need "ulimit -c unlimited" too.

Original comment by Anselm Kruis (Bitbucket: akruis, GitHub: akruis):

---

Removing milestone: 3.4.2-slp (automated comment)

Original comment by Anselm Kruis (Bitbucket: akruis, GitHub: akruis):

---

Now that #103 is resolved, all the test suite of 3.4-slp passes without errors introduced by Stackless. At least in my tests.