Closed issue by ACR-Jeff on void-packages repository

https://github.com/void-linux/void-packages/issues/49270

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.18_1 x86_64 AuthenticAMD uptodate rmFFFFFFFF

### Package(s) Affected

cpulimit-0.2_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

The latest I could find is back in 2016 in cpulimit issues https://github.com/opsengine/cpulimit/issues?q=segmentation+fault

Maybe this will help get some info to resolve with the void-package, I solved it temporarily by Downloading an updated version `cpulimit_2.8-1_amd64.deb` from debian bookworm packages and installing with xdeb `https://github.com/xdeb-org/xdeb`

### Expected behaviour

Expecting `cpulimit --exe=processname -l 500` (changing 'processname' with actual process name) to limit a process to not use over the 500 value of cpu usage.

### Actual behaviour

When using cpulimit and a set of arguments example: `cpulimit --exe=processname -l 500` within the terminal it prints 'Segmentation Fault'. I have tested also with `sudo cpulimit -e=processname -l 500` which has the same results.

### Steps to reproduce

1. Installing cpulimit `./xbps-src pkg cpulimit`
2. sudo xbps-install -R hostdir/binpkgs cpulimit
3. Execute a process to test cpulimit
4. Open Terminal
5. exec cpulimit within terminal `cpulimit --exe=processname -l 500` 
6. changing 'processname' with actual process name before executing
7. Results `Segmentation Fault`