-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iperf3: segfault on x86_64 #24668
Comments
I forgot to mention @nbd168 (had to edit the post above) |
This seems like an upstream issue? I can reproduce it with other linux distros as well |
how did you reproduce it? Just by running iperf3 or a special command? |
@Djfe see upstream
I get this seg fault when i abruptly stop the client from performing the iperf test and then resuming with another client on the same port |
Not fixed by 37ade7e ? |
@neheb x86_64 is little endian so that fix isn't applicable |
It relates to JSON code. Anyway, gdb is needed to figure this out. |
This is still an issue in current snapshots for this architecture.
|
is crashing on my mipsel device. Will investigate. |
I'm getting
I have a strong feeling esnet/iperf@3da07ae fixes it |
Yep, will push. |
Maintainer: @nbd168
Environment: x86_64, Hewlett-Packard HP EliteDesk 800 G1 USDT, OpenWrt GCC 12.3.0 r23899+10-3001d3c5d4
This was an OpenWrt fork: Gluon v2023.2.3
Which runs:
Description:
I just noticed this segfault in dmesg after running a couple of iperf3 commands (I'm not sure which one triggered it or if it could've been triggered by a STRG+C by accident)
The text was updated successfully, but these errors were encountered: