Sometimes some versions of the shared libraries that are part of the
traceback are compiled in optimised mode and the Program Counter (PC)
is not present, not allowing gdb to walk the frames back. When this
happens, the Python bindings of gdb raise an exception, making the
test impossible to succeed.

This reverts commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287.

When Python is built with the intel control-flow protection flags,
-mcet -fcf-protection, gdb is not able to read the stack without
actually jumping inside the function. This means an extra
'next' command is required to make the $pc (program counter)
enter the function and make the stack of the function exposed to gdb.

* Remove Setup.config
* Always define WITH_THREAD for compatibility.

Calling builtin method is at most 10% faster.

Issue #29367. On Python 2, __init__ name is render as u'__init__'.

Issue #29367. Use two break points to prevent breakpoint during Python
initialization.

Issue #29367: python-gdb.py now supports also method-wrapper (wrapperobject)
objects.

Issue #29259:

* Detect PyCFunction is the current frame, not only in the older frame
* Ignore PyCFunction_Call() since it now calls _PyCFunction_FastCallDict(), and
  _PyCFunction_FastCallDict() is already detected

Frame.is_other_python_frame() now also handles _PyCFunction_FastCallDict()
frames.

Thanks to the new code to handle fast calls, python-gdb.py is now also able to
detect the <built-in id method of module ...> frame.