[issue43941] Unit test failure in test_gdb only with -O0

Skip Montanaro added the comment: Unfortunately, I'm currently not able to build Python 3.8, 3.9 or 3.10 and get a non-failing test_gdb. I'll mess around a bit more, but I'm skeptical I'll find something simple. (I wonder if something changed in GDB which is causing the failure.) --

[issue43941] Unit test failure in test_gdb only with -O0

Pablo Galindo Salgado added the comment: Skip: I am still unable to reproduce in my machine unfortunately. Could you maybe bisect the failures if you can reliably reproduce the problem so we can at least narrow it down to one commit? -- ___ Python

[issue43941] Unit test failure in test_gdb only with -O0

Skip Montanaro added the comment: I routinely build with -O0 and have been getting test_gdb failures building the 3.10 branch. I tried adding -g3 to my configure flags: nice ./configure OPT="-O0 -g3 -Wall" --with-pydebug --with-trace-refs but test_gdb still fails. Output attached. Note that

[issue43941] Unit test failure in test_gdb only with -O0

Pablo Galindo Salgado added the comment: I will try to reproduce this in other systems this afternoon. I trust that this fails, but we must know exactly what triggers this first. -- ___ Python tracker _

[issue43941] Unit test failure in test_gdb only with -O0

Larry Hastings added the comment: Did that. Well, technically, I replaced two lines with the equivalent: % CFLAGS='-O0 -g3' ./configure I do see this in the Makefile: CONFIGURE_CFLAGS= -O0 -g3 so, I didn't screw it up! The test still failed: ==

[issue43941] Unit test failure in test_gdb only with -O0

Pablo Galindo Salgado added the comment: Can you try to do this: % make distclean % export CFLAGS='-O0 -g3' % ./configure % make -j % ./python -m test test_gdb -m test_wrapper_call -v My guess is that the DWARF generated is not sufficient for whatever reason (hence the -g3) in my proposal.

[issue43941] Unit test failure in test_gdb only with -O0

Larry Hastings added the comment: I'm on "Pop!_OS 20.10". Current versions: * Linux kernel 5.11.0-7612 * gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) * GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2 % ./python -m sysconfig | grep CFLAGS BASECFLAGS = "-Wno-unused-result -Wsign-compare" CF

[issue43941] Unit test failure in test_gdb only with -O0

Pablo Galindo Salgado added the comment: Thanks, Larry for pinging me! What compiler / gdb version are you using? I tried to reproduce but I don't see any failure: master on  master [$]  pyenv 3.9.1 took 9s ❯ ./python -m sysconfig | grep CFLAGS BASECFLAGS = "-Wno-unused-result -Wsig

[issue43941] Unit test failure in test_gdb only with -O0

New submission from Larry Hastings : Recent Python source trees fail a regression test in test_gdb. Oddly, the behavior only appears up when optimization is turned off. To reproduce: % git clone cpython buildtrunk % cd buildtrunk % ./configure % vi Makefile # change "-O3" to "-O0" !! % make