From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 423B33858C35; Sun, 31 Dec 2023 20:32:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 423B33858C35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704054721; bh=oQPj+FZj/DZf9YPckrM6GeADzk+46bJqj8SPI/R1oOw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=iViFb622U+mR6s83Pu3ZsMnAlv3rhDFTTG2yt+yHo3NPSfrsAS9HeOT2ntl6/PaUY GmawMQIpTtwuIkEvh8FABVWowwzZfeLEpzW7kgHcjRdx7cAT5C/rMALc1z7xtutT5f YWat5wvxwmf8aG4DK3BDCDeaiu3Hq6v+1sfxiy2o= From: "chris_douglas_email at yahoo dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/31152] Formalise unintened functionality in version 9.1 Date: Sun, 31 Dec 2023 20:32:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 14.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: chris_douglas_email at yahoo dot com X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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=3D31152 --- Comment #7 from stephen douglas = --- Created attachment 15275 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D15275&action=3Ded= it Unified difference file to detect cause of segment trap in event-loop.cc This will error before the segment trap I encountered in event-loop.cc and would have provided me with enough information to prevent it. I have always used gbd from a cli on the target so don't know if this will prevent a segm= ent trap if run/gdbserver combination is being used. If you want to understand, the online manual https://man7.org/linux/man-pages/man2/select.2.html explains under the head= ing BUGS. The file descriptor limitation is in glibc, not the kernel. If the ke= rnel has not been "tampered with" the condition can not occur. As stated earlier, my usage is unusual and uncommon. There are other occura= nces of the 3 macros that can cause a memmory access outside fd_set with a "problematic" file descriptor. The macro FD_ZERO uses FD_SETSIZE so can not access outside fd_set. --=20 You are receiving this mail because: You are on the CC list for the bug.=