[v11] Add pretty printers for the NPTL lock types
Commit Message
I have committed this now, with the NEWS block below.
Thank you for your patience and commitment!
Siddhesh
On ARM EABI (32-bit), generating a backtrace for execution contexts which
Comments
After a build and test run I see files scripts/test_printers_common.pyc
and scripts/test_printers_exceptions.pyc created in the source directory.
We'd like to be able to build with read-only source directories, could the
tests be fixed not to create .pyc files (e.g. use python -B) or to create
them in the build directory?
On Thu, Dec 8, 2016 at 18:56, Joseph Myers wrote:
> After a build and test run I see files scripts/test_printers_common.pyc
> and scripts/test_printers_exceptions.pyc created in the source directory.
> We'd like to be able to build with read-only source directories, could the
> tests be fixed not to create .pyc files (e.g. use python -B) or to create
> them in the build directory?
Sure, feel free to do so. I believe you could achieve that by setting PYTHON to 'python -B' in Rules, or maybe defining a separate PYTHONFLAGS variable.
I'd love to do it myself but I don't have access to a testing machine right now. It's a small change though, so it shouldn't be an issue.
@@ -141,6 +141,11 @@ Version 2.25
variable for a particular architecture in the GCC source file
'gcc/config.gcc'.
+* GDB pretty printers have been added for mutex and condition variable
+ structures in POSIX Threads. When installed and loaded in gdb these
pretty
+ printers show various pthread variables in human-readable form when read
+ using the 'print' or 'display' commands in gdb.
+
Security related changes: