Confirmed. Was able to get a segfault on a mac with this code: import time from Phidget22.Phidget import * from Phidget22.Devices.DistanceSensor import * # Event handler for when the sensor has a new distance value def onDistanceChange(distanceSensor, userData): print(f"Distance: {distanceSenso...

distance_sensor.setOnDistanceChangeHandler(None) distance_sensor.setOnDistanceChangeHandler(BlahSensor.on_distance_change) Seems like the code's author (not me) is setting the OnDistanceChangeHandler to None and then to a certain method repeatedly in the code. This seems fishy to me, and I'll chang...

I'll post more information once I have it, probably on Wednesday.

No Python stack-trace was provided presumably because I didn't have "faulthandler" enabled and the segfault happened in a non-main thread.

Thanks for the help!

I'm getting a SEGFAULT: #0 0x000000003b9acc04 in ?? () #1 0x0000000000494468 in _PyObject_MakeTpCall () #2 0x0000007fab656910 in ?? () from /usr/lib/python3.11/lib-dynload/_ctypes.cpython-311-aarch64-linux-gnu.so #3 0x0000007fab616190 in ?? () from /lib/aarch64-linux-gnu/libffi.so.8 #4 0x0000007fab6...

In the code below, if I ctrl^c, the message "Got KB interrupt" is not shown. If I comment out the "scale.openWai..." line, then "Got KB interrupt" is shown when I ctrl^C. The normal control-flow of the program should not be changed just because a Phidget is being used. ...