Hi,

I am using cvblob on an ARM processor, and I discovered a bug in the code. It seems ARM uses an unsigned char by default, while x86 uses signed char.

This leads to an infinite loop in the contour-finding loop in cvLabel.

Specifically, in cvlabel.cpp, on lines 34 and 40, I changed const char movesE ... const char movesI ...

to

const signed char movesE ... const signed char movesI ...

And now it seems to work. However, I haven't yet checked the rest of the code for problems. Perhaps a solution would be to change the Makefile to compile with '-fsigned-char'.

Hi!

Thank you very much for the report and for the solutions. I will consider both solutions.

I confirm what has been said by grendel....@gmail.com. I had the same problems and his workaround helped! Thank you very much grendel! cheers s.

I also had the same problem! thanks all!

Similar issue for ARM (et al.?) processors,

cvBlob/cvcontour.cpp , line 84:

change

const char cvChainCodeMoves[8][2] = { { 0, -1},

to

const signed char cvChainCodeMoves[8][2] = { { 0, -1},

(loses the sign on ARM which causes problems later)

Cheers,

Doug

Thanks so much for pointing out the bug in cvLabel for ARM processors. I had given up on my Raspberry Pi ever working with cvBlob. I should have read this issue and saved myself hours of troubleshooting! It fixed the problem I had with cvLabel. Brilliant! Thanks.

Thank you very much for this fix, you have saved my graduation! However this fix should be mainstreamed into the source code, and not have to make future users have to find the fix through Google.

Hello someone please help me regarding cross compilation of cvBlob for arm.I stucked on it for many days. Thanks in advance

Thank you so much for the workaround!

OMG thank you very much!! I was in the same situation as gary now, i finally have something working on my Raspberry Pi =D

Thank you so much!