[Bug gdb/31152] Formalise unintened functionality in version 9.1

["chris_douglas_email at yahoo dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31152

--- Comment #7 from stephen douglas <chris_douglas_email at yahoo dot com> ---
Created attachment 15275
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15275&action=edit
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 segment
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 heading
BUGS. The file descriptor limitation is in glibc, not the kernel. If the kernel
has not been "tampered with" the condition can not occur.

As stated earlier, my usage is unusual and uncommon. There are other occurances
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.