[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-25 Thread Łukasz Langa
Changes by Łukasz Langa : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___

[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-25 Thread Łukasz Langa
Łukasz Langa added the comment: I guess it's wontfix then. Sad, since that leaves us partially blind to regressions like bpo-30983. -- ___ Python tracker

[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-21 Thread Dave Malcolm
Dave Malcolm added the comment: The problem is that there are so many variables: * which version of which compiler * optimization flags * which version of gdb * which CPU architecture etc (and the compiler and/or gdb could be carrying patches from downstream distributors...) All of these can

[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-21 Thread Antoine Pitrou
Antoine Pitrou added the comment: I don't think it's a surprise that reconstructing high-level program information from a debugger works less well on optimized builds. Perhaps Dave Malcolm has more precise information about what is supposed to to work and what is not. -- nosy:

[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-21 Thread Łukasz Langa
Łukasz Langa added the comment: You're being vague, can you say which optimized builds and which data? As I mentioned, builds that actual users use are almost always compiled without --with-pydebug. That includes, say, the default RedHat python RPMs or the Debian DEBs that ship with those

[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-18 Thread STINNER Victor
STINNER Victor added the comment: Sadly, python-gdb fails to get required data for some commands, so python-gdb doesn't work fully on optimized builds. -- ___ Python tracker

[issue31237] test_gdb disables 25% of tests in optimized builds

2017-08-18 Thread Łukasz Langa
New submission from Łukasz Langa: We are skipping a lot of tests when optimizations are enabled (which essentially means: compiled without `--with-pydebug`). This seems overly aggressive since most Python users are using the gdb bindings with a non-debug build. I think we should have tests