bad ISR initialisation about pigpio HOT 4 CLOSED

That is just a plain error on my part.

The erroneous error is because of an incorrect check when the GPIO is unexported. The unexport itself will be fine. However a consequential error means the GPIO is still marked exported internally and the software will not set up a new ISR.

The line

if (err != sizeof(buf)) return PI_BAD_ISR_INIT;

should be

if (err != strlen(buf)) return PI_BAD_ISR_INIT;

in the intGpioSetISRFunc function.

I'll correct the software in the next release (probably before 27th Oct 15).

from pigpio.

Great, thanks.

from pigpio.

Implemented in V39.

from pigpio.

Thanks for fixing this. Everything looks a lot better now and the issue has been resolved. However, there is a new issue.

Here's the output of the first run of the test program from the original post:

version: 39
isr1 - gpio: 4, level: 2
isr1 - gpio: 4, level: 2
isr1 - gpio: 4, level: 2
isr1 - gpio: 4, level: 2
isr2
isr2
isr2
isr2
2015-10-31 07:08:41 sigHandler: Unhandled signal 11, terminating

Here's the output of the second run:

2015-10-31 07:09:23 initMboxBlock: init mbox zaps failed

As can be seen, everything isn't quite right yet. However, this is a different problem so I'll open a new issue for it.

This problem can be solved by calling gpioSetISRFunc(GPIO, EITHER_EDGE, 0, NULL) directly before calling gpioTerminate().

from pigpio.