Ubuntu 24.04 glibc Fortification at runtime problem.

[videoman]

Problem: after building, and starting a config, Hercules would immediately show this error after starting:

HHC00100I Thread id 0000754ea2ffb6c0, prio -1, name 'console_connect' started
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated

Version information:
HHC01413I Hercules version 4.10.0.11676-SDL-DEV-gad45f430

• Ubuntu 24.04 / kernel 6.8.0:

• uname -a
  Linux my-vm 6.8.0-107-generic #107-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 13 19:51:50 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux

• ldd (Ubuntu GLIBC 2.39-0ubuntu8.7) 2.39

Fix for building from hercules-helper (I've already submitted an issue to them as well):

cd ~/herctest
export CFLAGS="-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0"
~/hercules-helper/hercules-buildall.sh --auto --flavor=sdl-hyperion

In Ubuntu 24.04 after turning off fortification, Hercules now runs.

Long-term might need to use the poll() functions instead of the select() functions in the console thread.

YMMV.

Happy to provide additional details if necessary.

[wrljet]

I will take a look at this, in both places. Thanks for reporting it.

Bill

[wrljet]

Is this fortification something you need to enable in Ubuntu 24.04? I've never run into this before.

[gottfriedleibniz]

Similarly, this is something I have also hit running Hercules w/ valgrind, e.g.,

22:39:27 HHC90508D COMM: pselect() failed: Bad address

While I have not yet investigated the issue, it generally makes sense both tools are aligned here.

Update: valgrind's report seems like a false-positive.

[wrljet]

Happy to provide additional details if necessary.

You'll need to tell me how to turn on this fortification feature.

[wrljet]

@videoman Still waiting for an answer here.