From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D10323858D37; Wed, 30 Nov 2022 18:09:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D10323858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669831787; bh=K/ufmwOoXnlhyKVUC1RPxSi64W3TxRtcMaB1a2cOgqk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=q8/rSDwtGoyuoQpVFQpKnZ68Rh+EZDhLhT998B7dKFcmGOfO6k0jkfUxZBDn9jvNT HNVmhIlZeTxSr4BBsFYS3RcYUIPOHu9J6WjA7i6mI8+TckKRlKbhsYZw00tbYtgCz/ ZC18vDBbcQuxqv4WShBLPUYOaZsZonxw0dVs0bpU= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug compile/29541] gdb.compile/compile-cplus-anonymous.exp shows failures with glibc debuginfo installed Date: Wed, 30 Nov 2022 18:09:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: compile X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot 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: cc Message-ID: In-Reply-To: References: 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=3D29541 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- I've run into this recently. Looking into it, I see that the gdb plugin can hang while waiting for results from gcc. This happens due in a select() call... this is unfortunate, to say the least. I'm also disappointed in my past self because there doesn't seem to be any sort of sensible error-reporting system in the gdb plugin. That is, if a call fails, gdb will never really know about it, but instead will happily continue trying to exercise the API using nonsense :( Meanwhile I do at least have a workaround for the test suite timeouts. These have been a real pain. --=20 You are receiving this mail because: You are on the CC list for the bug.=