Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_gdb fails on armv7hl #61937

Closed
bkabrda mannequin opened this issue Apr 15, 2013 · 3 comments
Closed

test_gdb fails on armv7hl #61937

bkabrda mannequin opened this issue Apr 15, 2013 · 3 comments
Labels
tests Tests in the Lib/test dir type-bug An unexpected behavior, bug, or error

Comments

@bkabrda
Copy link
Mannequin

bkabrda mannequin commented Apr 15, 2013

BPO 17737
Nosy @vstinner, @davidmalcolm

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2020-06-11.13:21:15.658>
created_at = <Date 2013-04-15.13:41:08.564>
labels = ['type-bug', 'tests']
title = 'test_gdb fails on armv7hl'
updated_at = <Date 2020-06-11.13:21:15.656>
user = 'https://bugs.python.org/bkabrda'

bugs.python.org fields:

activity = <Date 2020-06-11.13:21:15.656>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2020-06-11.13:21:15.658>
closer = 'vstinner'
components = ['Tests']
creation = <Date 2013-04-15.13:41:08.564>
creator = 'bkabrda'
dependencies = []
files = []
hgrepos = []
issue_num = 17737
keywords = []
message_count = 3.0
messages = ['186987', '187076', '371273']
nosy_count = 3.0
nosy_names = ['vstinner', 'dmalcolm', 'bkabrda']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17737'
versions = ['Python 3.4', 'Python 3.5']

@bkabrda
Copy link
Mannequin Author

bkabrda mannequin commented Apr 15, 2013

Hi,
it seems that test_gdb fails on armv7hl on Fedora 19 and 20 [1] (I'm also tracking my notes of the bug there). Basically, the problem seems to come down to PyObjectPtr.subclass_from_type (file python-gdb.py) returning different values for members of the stack trace (compared to successful builds - see [3] for x86_64 successful build and [4] for armv7hl failed build).
The two failed tests fail with:

======================================================================
FAIL: test_up_at_top (test.test_gdb.StackNavigationTests)
Verify handling of "py-up" at the top of the stack
----------------------------------------------------------------------

Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-3.3.1/Lib/test/test_gdb.py", line 678, in test_up_at_top
    cmds_after_breakpoint=['py-up'] * 4)
  File "/builddir/build/BUILD/Python-3.3.1/Lib/test/test_gdb.py", line 213, in get_stack_trace
    self.assertEqual(err, '')
AssertionError: "Python Exception <class '__main__.NullPyObjectPtr'> <__main__.PyFrameObjectPtr  [truncated]... != ''
- Python Exception <class '__main__.NullPyObjectPtr'> <__main__.PyFrameObjectPtr object at 0x23a6db0>: 
- Error occurred in Python command: <__main__.PyFrameObjectPtr object at 0x23a6db0>

======================================================================
FAIL: test_threads (test.test_gdb.PyBtTests)
Verify that "py-bt" indicates threads that are waiting for the GIL
----------------------------------------------------------------------

Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-3.3.1/Lib/test/test_gdb.py", line 759, in test_threads
    cmds_after_breakpoint=['thread apply all py-bt'])
  File "/builddir/build/BUILD/Python-3.3.1/Lib/test/test_gdb.py", line 213, in get_stack_trace
    self.assertEqual(err, '')
AssertionError: "Python Exception <class 'gdb.error'> There is no member named co_name.: \nError [truncated]... != ''
- Python Exception <class 'gdb.error'> There is no member named co_name.: 
- Error occurred in Python command: There is no member named co_name.

The whole build log is accessible at [2]. Any clues would be appreciated. Thanks.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=951802
[2] http://arm.koji.fedoraproject.org//work/tasks/2722/1712722/build.log
[3] https://gist.github.com/bkabrda/5387906
[4] https://gist.github.com/bkabrda/5387908

@bkabrda bkabrda mannequin added the tests Tests in the Lib/test dir label Apr 15, 2013
@bkabrda
Copy link
Mannequin Author

bkabrda mannequin commented Apr 16, 2013

This may also be related to the tests failing on official buildbots as mentioned in [1], although the error messages look different. However both of these issues seem to be a memory corruption problem, as one of the frames in stack trace (the one that fails the tests for me) has ob_refcnt < 0 and ob_type = 0x26000000, (corresponds to tuple if I'm not mistaken) and all sorts of other weird values.

[1] http://bugs.python.org/issue12605#msg166423

@BreamoreBoy BreamoreBoy mannequin added the type-bug An unexpected behavior, bug, or error label Jul 5, 2014
@vstinner
Copy link
Member

Python 3.4 and Fedora 20 are no longer maintained. See bpo-40746 for a more recent test_gdb issue on armv7l.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Tests in the Lib/test dir type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

1 participant