From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 499CC3858D20; Mon, 29 Jan 2024 15:41:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 499CC3858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1706542885; bh=OvKdYMZF5uPtvzB3yqCaXJJI2vIvNpxInnA+7Cachuw=; h=From:To:Subject:Date:From; b=yD5Gn33TO0J26hKrwkg/rgYmZEhP+PDieYiY9ot+xnyW0qKVxyCFIbUBI/cWsl2Vs /tDlhfjDiEZ4NL9aC4QNqcP5MPRCjwUGSJocpGrMQqlM2qbJpI7I6xjfLGL8/fq57S BRNHf6PJqnwSMvoAw+vlTHc2jZ5a/KGCR1fMpq6A= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/31310] New: [gdb/testsuite] FAIL: gdb.base/siginfo-thread.exp: extract si_errno Date: Mon, 29 Jan 2024 15:41:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31310 Bug ID: 31310 Summary: [gdb/testsuite] FAIL: gdb.base/siginfo-thread.exp: extract si_errno Product: gdb Version: 13.1 Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With gdb 13.2-based package, on s390x-linux I ran into: ... 2 =3D {si_signo =3D 11, si_errno =3D -701448376, si_code =3D 2, _sifields = =3D {_pad =3D {1023, -33583104, 0, 18018696, 0, 688795888, 1023, -606613560, 0, 0, 0, 1, = 0, 690096224, 0, 0, 1023, -1732204328, 1023, -1733240784, 1023, -606614648, 0, 688638048, 0, 688854112, 0, 30292512}, _kill =3D {si_pid =3D 1023, si_uid = =3D 4261384192}, _timer =3D {si_tid =3D 1023, si_overrun =3D -33583104, si_sigv= al =3D {sival_int =3D 0, sival_ptr =3D 0x112f188}}, _rt =3D {si_pid =3D 1023, si_u= id =3D 4261384192, si_sigval =3D {sival_int =3D 0, sival_ptr =3D 0x112f188}}, _sig= chld =3D {si_pid =3D 1023, si_uid =3D 4261384192, si_status =3D 0, si_utime =3D 77389710036566016, si_stime =3D 2958355812579279871}, _sigfault =3D {si_add= r =3D 0x3fffdff9000}, _sigpoll =3D {si_band =3D 4398012928000, si_fd =3D 0}, _sig= sys =3D {_call_addr =3D 0x3fffdff9000, _syscall =3D 0, _arch =3D 18018696}}}^M (gdb) FAIL: gdb.base/siginfo-thread.exp: extract si_errno ... This fails because errno is matched using: ... set test "extract si_errno" gdb_test_multiple "p \$_siginfo" "$test" { -re "si_errno =3D (\[0-9\]\+).*$gdb_prompt $" { set ssi_errno $expect_out(1,string) pass "$test" } } ... which doesn't account for the possibility that errno is negative. In linux_get_siginfo_type_with_fields I see: ... append_composite_type_field (siginfo_type, "si_errno", int_type); ... so I guess that should be permitted. --=20 You are receiving this mail because: You are on the CC list for the bug.=