[Bug] Segmentation Fault or Timeout Caused by the Combination of Multiple Parameters

[wyunc]

Describe the bug

Hi everyone,

I’ve identified four sets of configuration parameters that can cause the jmavsim software to crash. The details are as follows:

1. Setting these two parameters simultaneously results in a Segmentation Fault in jmavsim. param set EKF2_MAG_NOISE 10000.0 param set SENS_MAG_RATE 1.99

2. Setting these two parameters together causes the drone in jmavsim to crash and lose connection, with: ERROR [simulator_mavlink] poll timeout 0, 22 param set IMU_GYRO_NF0_BW 1232.18 param set IMU_GYRO_NF0_FRQ 4.76

3. After setting this pair of parameters, jmavsim delays for a few to several seconds and then triggers a Segmentation Fault. param set EKF2_GPS_POS_Y 159.81 param set EKF2_GPS_V_NOISE 10000.0

4. After setting this pair of parameters, jmavsim delays for a few to several seconds and then triggers a Segmentation Fault. param set EKF2_GPS_POS_Y 971.2 paramset EKF2_GPS_P_NOISE 10000.0

To Reproduce

No response

Expected behavior

No response

Screenshot / Media

Flight Log

No response

Software Version

PX4 version: 1.16.0 c0 (17825984)

and simulator: jmavsim

Flight controller

No response

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response

[DronecodeBot]

This issue has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/segmentation-fault-or-timeout-caused-by-the-combination-of-multiple-parameters/46000/1