#373 Sum reporting with -u and --reverse and -P > 1 has issues on both Mac and Linux

[Robert McMahon]

(lldb) run -c 192.168.1.34 -i 1 -e -l 200 -u -b 25M --reverse -P 4

There is a running process, kill it and restart?: [Y/n] y

Process 63102 exited with status = 9 (0x00000009) killed

Process 63109 launched: '/Users/rjmcmahon/Code/iperf2-code/src/iperf' (arm64)

------------------------------------------------------------

Client connecting to 192.168.1.34, UDP port 5001 with pid 63109 (4/0 flows/load)

TOS defaults to 0x0 (dscp=0,ecn=0) (Nagle on)

Sending 200 byte datagrams, IPG target: 0.00 us (kalman adjust)

UDP buffer size: 9.00 KByte (default)

------------------------------------------------------------

[  2] local 192.168.1.57%en0 port 53046 connected with 192.168.1.34 port 5001 (reverse) on 2025-03-18 20:49:39.509 (PDT)

[  1] local 192.168.1.57%en0 port 61482 connected with 192.168.1.34 port 5001 (reverse) on 2025-03-18 20:49:39.509 (PDT)

[  4] local 192.168.1.57%en0 port 56085 connected with 192.168.1.34 port 5001 (reverse) on 2025-03-18 20:49:39.509 (PDT)

[  3] local 192.168.1.57%en0 port 61665 connected with 192.168.1.34 port 5001 (reverse) on 2025-03-18 20:49:39.509 (PDT)

[ ID] Interval        Transfer     Bandwidth        Jitter   Lost/Total  Latency avg/min/max/stdev PPS Read/Timeo/NA NetPwr

[ *4] 0.00-1.00 sec  3.13 MBytes  26.2 Mbits/sec   0.032 ms 0/16389 (0%) -21.323/-21.375/-20.481/0.025 ms 16389 pps 16389/0/0 -153.722460

[ *2] 0.00-1.00 sec  3.13 MBytes  26.2 Mbits/sec   0.043 ms 0/16390 (0%) -21.292/-21.375/-20.889/0.039 ms 16390 pps 16390/0/0 -153.955598

[ *4] 1.00-2.00 sec  3.12 MBytes  26.2 Mbits/sec   0.025 ms 0/16383 (0%) -21.293/-21.378/-21.187/0.039 ms 8192 pps 16383/0/0 -153.883406

[ *1] 0.00-1.00 sec   675 KBytes  5.53 Mbits/sec   0.025 ms 0/3457 (0%) -21.294/-21.377/-21.166/0.039 ms 3457 pps 3457/1/0 -32.469137

Process 63109 stopped


* thread #2, stop reason = EXC_BAD_ACCESS (code=1, address=0x40ab01ffffffffa0)

    frame #0: 0x000000019d38c164 libsystem_platform.dylib`_platform_strlen + 4

libsystem_platform.dylib`_platform_strlen:

->  0x19d38c164 <+4>:  ldr    q0, [x1]

    0x19d38c168 <+8>:  adr    x3, 0x19d38c0a0 ; ___lldb_unnamed_symbol299

    0x19d38c16c <+12>: ldr    q2, [x3], #0x10

    0x19d38c170 <+16>: and    x2, x0, #0xf

Target 0: (iperf) stopped.

(lldb) bt


* thread #2, stop reason = EXC_BAD_ACCESS (code=1, address=0x40ab01ffffffffa0)


  * frame #0: 0x000000019d38c164 libsystem_platform.dylib`_platform_strlen + 4

    frame #1: 0x000000019d1ee74c libsystem_c.dylib`__vfprintf + 3580

    frame #2: 0x000000019d1fda00 libsystem_c.dylib`vfprintf_l + 156

    frame #3: 0x000000019d218c3c libsystem_c.dylib`printf + 80

    frame #4: 0x0000000100017bf4 iperf`udp_output_read_enhanced(stats=0x0000000136013240) at ReportOutputs.c:0 [opt]

    frame #5: 0x000000010000dbb4 iperf`reporter_transfer_protocol_server_udp(data=0x0000000136013200, final=<unavailable>) at Reporter.c:1535:2 [opt]

    frame #6: 0x00000001000100b0 iperf`reporter_condprint_time_interval_report(data=0x0000000136013200, packet=0x0000000138300250) at Reporter.c:2109:2 [opt]

    frame #7: 0x000000010000b294 iperf`reporter_process_transfer_report(this_ireport=0x0000000136013200) at Reporter.c:589:18 [opt]

    frame #8: 0x000000010000b8a8 iperf`reporter_process_report(reporthdr=0x0000600003398040) at Reporter.c:660:9 [opt]

    frame #9: 0x000000010000b810 iperf`reporter_spawn(thread=0x0000000134010800) at Reporter.c:506:14 [opt]

    frame #10: 0x000000010002c1d8 iperf`thread_run_wrapper(paramPtr=0x0000000134010800) at Thread.c:374:17

    frame #11: 0x000000019d3582e4 libsystem_pthread.dylib`_pthread_start + 136Bob