Staging
v0.5.1
v0.5.1
https://github.com/python/cpython
Revision 25bfb1aa75c8358becdab11142954c8ee9c3607f authored by Miss Islington (bot) on 09 October 2018, 15:20:38 UTC, committed by GitHub on 09 October 2018, 15:20:38 UTC
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. Co-Authored-By: Marcel Plch <gmarcel.plch@gmail.com> (cherry picked from commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287) (cherry picked from commit 79d21331e605fdc941f947621846b8563485aab6) Co-authored-by: Victor Stinner <vstinner@redhat.com>
1 parent 64bcedc
Tip revision: 25bfb1aa75c8358becdab11142954c8ee9c3607f authored by Miss Islington (bot) on 09 October 2018, 15:20:38 UTC
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (GH-9656)
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (GH-9656)
Tip revision: 25bfb1a
| File | Mode | Size |
|---|---|---|
| Python.asdl | -rw-r--r-- | 5.0 KB |
| acceler.c | -rw-r--r-- | 3.3 KB |
| asdl.py | -rw-r--r-- | 12.6 KB |
| asdl_c.py | -rw-r--r-- | 43.7 KB |
| bitset.c | -rw-r--r-- | 1.0 KB |
| firstsets.c | -rw-r--r-- | 2.8 KB |
| grammar.c | -rw-r--r-- | 7.4 KB |
| grammar1.c | -rw-r--r-- | 1.3 KB |
| listnode.c | -rw-r--r-- | 1.2 KB |
| metagrammar.c | -rw-r--r-- | 2.4 KB |
| myreadline.c | -rw-r--r-- | 10.1 KB |
| node.c | -rw-r--r-- | 4.4 KB |
| parser.c | -rw-r--r-- | 11.6 KB |
| parser.h | -rw-r--r-- | 1.0 KB |
| parsetok.c | -rw-r--r-- | 10.5 KB |
| parsetok_pgen.c | -rw-r--r-- | 35 bytes |
| pgen.c | -rw-r--r-- | 17.9 KB |
| pgenmain.c | -rw-r--r-- | 4.0 KB |
| printgrammar.c | -rw-r--r-- | 2.9 KB |
| tokenizer.c | -rw-r--r-- | 54.6 KB |
| tokenizer.h | -rw-r--r-- | 3.8 KB |
| tokenizer_pgen.c | -rw-r--r-- | 36 bytes |
Computing file changes ...
