Description of problem: Verify that the "py-up" command works ... skipped 'Python was compiled with optimizations' Verify that "py-bt" indicates threads that are waiting for the GIL ... FAIL test_basic_command (__main__.PyPrintTests) Verify that the "py-print" command works ... skipped 'Python was compiled with optimizations' test_print_after_up (__main__.PyPrintTests) ... skipped 'Python was compiled with optimizations' test_printing_builtin (__main__.PyPrintTests) ... skipped 'Python was compiled with optimizations' test_printing_global (__main__.PyPrintTests) ... skipped 'Python was compiled with optimizations' test_basic_command (__main__.PyLocalsTests) ... skipped 'Python was compiled with optimizations' test_locals_after_up (__main__.PyLocalsTests) ... skipped 'Python was compiled with optimizations' ====================================================================== FAIL: test_threads (__main__.PyBtTests) Verify that "py-bt" indicates threads that are waiting for the GIL ---------------------------------------------------------------------- Traceback (most recent call last): File "./Lib/test/test_gdb.py", line 758, in test_threads cmds_after_breakpoint=['thread apply all py-bt']) File "./Lib/test/test_gdb.py", line 212, in get_stack_trace self.assertEqual(unexpected_errlines, []) AssertionError: Lists differ: ['Cannot access memory at addr... != [] First list contains 4 additional elements. First extra element 0: Cannot access memory at address 0x0 + [] - ['Cannot access memory at address 0x0', - 'Cannot access memory at address 0x0', - "Python Exception <class 'gdb.error'> Frame is invalid.: ", - 'Error occurred in Python command: Frame is invalid.'] ---------------------------------------------------------------------- Ran 45 tests in 105.321s FAILED (failures=1, skipped=15) Traceback (most recent call last): File "./Lib/test/test_gdb.py", line 887, in <module> test_main() File "./Lib/test/test_gdb.py", line 883, in test_main PyLocalsTests File "/builddir/build/BUILD/Python-3.3.2/Lib/test/support.py", line 1592, in run_unittest _run_suite(suite) File "/builddir/build/BUILD/Python-3.3.2/Lib/test/support.py", line 1567, in _run_suite raise TestFailed(err) test.support.TestFailed: Traceback (most recent call last): File "./Lib/test/test_gdb.py", line 758, in test_threads cmds_after_breakpoint=['thread apply all py-bt']) File "./Lib/test/test_gdb.py", line 212, in get_stack_trace self.assertEqual(unexpected_errlines, []) AssertionError: Lists differ: ['Cannot access memory at addr... != [] First list contains 4 additional elements. First extra element 0: Cannot access memory at address 0x0 + [] - ['Cannot access memory at address 0x0', - 'Cannot access memory at address 0x0', - "Python Exception <class 'gdb.error'> Frame is invalid.: ", - 'Error occurred in Python command: Frame is invalid.'] [103998 refs] Version-Release number of selected component (if applicable): python3-3.3.2-3.fc20
Is this the same as https://bugzilla.redhat.com/show_bug.cgi?id=951802 ?
(In reply to Brendan Conoboy from comment #1) > Is this the same as https://bugzilla.redhat.com/show_bug.cgi?id=951802 ? Nah, this looks completely different. @CC Dave, do you have any idea what might cause this? (note: there is a distinct possibility that my downstream patch [1] might influence this, but IMO it is not the case) [1] http://pkgs.fedoraproject.org/cgit/python3.git/commit/?h=f19&id=b935d25938262c5161ab89752972f642f7dea5b6
as a temporary workaround im disabling the test so we can move forward. we do need to get it fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
(In reply to Bohuslav "Slavek" Kabrda from comment #2) > (In reply to Brendan Conoboy from comment #1) > > Is this the same as https://bugzilla.redhat.com/show_bug.cgi?id=951802 ? > > Nah, this looks completely different. @CC Dave, do you have any idea what > might cause this? > (note: there is a distinct possibility that my downstream patch [1] might > influence this, but IMO it is not the case) > > [1] > http://pkgs.fedoraproject.org/cgit/python3.git/commit/ > ?h=f19&id=b935d25938262c5161ab89752972f642f7dea5b6 [Clearing out the needinfo request] Sadly, there are many ways in which the gdb script can fail: it's affected by the version of gcc and the optimization flags used, and the version of gdb. FWIW, it looks like the gdb hooks were trying to dereference a null pointer in the inferior process.