public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "chris_douglas_email at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31152] Formalise unintened functionality in version 9.1 Date: Wed, 27 Dec 2023 19:22:11 +0000 [thread overview] Message-ID: <bug-31152-4717-8geKLjuVPS@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31152-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31152 --- Comment #3 from stephen douglas <chris_douglas_email at yahoo dot com> --- Created attachment 15272 --> https://sourceware.org/bugzilla/attachment.cgi?id=15272&action=edit Command line output The version I was able to use was 9.2 i.e. not 9.1 as in the initial report. The segment trap that was problematic to me was in event-loop.cc. It had correcly detected that I could not use poll so was attempting to use select. Unfortunatly macros FD_SET, FD_CLR and FD_ISSET access data outside the data structure if the file descriptor is NOT less than FD_SETSIZE. The root cause is that the commercially modified linux kernel that I was attempting to use encrypts file descriptors, so I was lucky that the encryption did not make the file descryptor too large on the old version. As stated in earlier comments my useage is unusual so I would understanf if this was closed, as invalid, without update for protection against the segment trap. However, once the segment trap was fixed (by updating glibc so FD_SETSIZE was larger than the standard value), I did get a warning (see attachment). The warning is not present in the old version. On "bare metal" build, only built in conversions are available in iconv i.e. UTF-32BE & UTF-32LE are not available. However UCS-4BE & UCS-4LE are available. My reading of the 2 sets of specifications are that they are equivelent. I would alsounderstand if this was closed with no action on this issue. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-27 19:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 18:16 [Bug gdb/31152] New: " chris_douglas_email at yahoo dot com 2023-12-12 20:31 ` [Bug gdb/31152] " tromey at sourceware dot org 2023-12-12 20:31 ` tromey at sourceware dot org 2023-12-27 19:22 ` chris_douglas_email at yahoo dot com [this message] 2023-12-28 16:44 ` tromey at sourceware dot org 2023-12-30 20:12 ` chris_douglas_email at yahoo dot com 2023-12-30 22:34 ` tromey at sourceware dot org 2023-12-31 20:32 ` chris_douglas_email at yahoo dot com 2024-01-14 16:45 ` chris_douglas_email at yahoo dot com
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-31152-4717-8geKLjuVPS@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).