public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30519] New: [gdb, i586] FAIL: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: test default value Date: Tue, 06 Jun 2023 09:33:26 +0000 [thread overview] Message-ID: <bug-30519-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30519 Bug ID: 30519 Summary: [gdb, i586] FAIL: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: test default value Product: gdb Version: 13.1 Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With a gdb 13.1 based package, on i586 native I run into: ... (gdb) python^M >PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 1: python class TestNodocParam (gdb.Parameter):^M >PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 2: class TestNodocParam (gdb.Parameter): def __init__ (self, name):^M >PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 3: def __init__ (self, name): super (TestNodocParam, self).__init__ (name, gdb.COMMAND_DATA, gdb.PARAM_UINTEGER)^M >PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 4: super (TestNodocParam, self).__init__ (name, gdb.COMMAND_DATA, gdb.PARAM_UINTEGER) self.value = 0^M >PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 5: self.value = 0 test_param_PARAM_UINTEGER = TestNodocParam ('test-PARAM_UINTEGER')^M >PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 6: test_param_PARAM_UINTEGER = TestNodocParam ('test-PARAM_UINTEGER') end^M Traceback (most recent call last):^M File "<string>", line 5, in <module>^M File "<string>", line 4, in __init__^M RuntimeError: Range exceeded.^M Error while executing Python code.^M (gdb) PASS: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: create parameter: input 7: end python print(test_param_PARAM_UINTEGER.value)^M Traceback (most recent call last):^M File "<string>", line 1, in <module>^M NameError: name 'test_param_PARAM_UINTEGER' is not defined^M Error while executing Python code.^M (gdb) FAIL: gdb.python/py-parameter.exp: test_integer_parameter: kind=PARAM_UINTEGER: test default value ... -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-06-06 9:33 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30519-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).