KX2 bug | developer.brewmp.com KX2 bug | developer.brewmp.com

Developer

KX2 bug

Forums:

We just solved a very strange bug on the KX2--

given int a; int b;

if a > -1 && b > a

the following operation causes PHONE CRASH / REBOOT
a-=b; //causes reboot

can anyone else confirm this?

I prefered you check your code for memery violation, I think there must be memory access error or index out of range of array.

I prefered you check your code for memery violation, I think there must be memory access error or index out of range of array.

The variable we found this applies to in our particular game is used for player health and is not used to index an array or otherwise manipulate any pointers.
It might be used for the width of a rect for IDISPLAY_FillRect(), ie: the health bar-- in which perhaps this means the device fails on FillRect() with negative widths. It was also being used in conjunction with FDIV().
This didnt cause any errors on 15 other handsets, just the KX2, so its definately a device issue no matter what the particular.

The variable we found this applies to in our particular game is used for player health and is not used to index an array or otherwise manipulate any pointers.
It might be used for the width of a rect for IDISPLAY_FillRect(), ie: the health bar-- in which perhaps this means the device fails on FillRect() with negative widths. It was also being used in conjunction with FDIV().
This didnt cause any errors on 15 other handsets, just the KX2, so its definately a device issue no matter what the particular.

keless wrote:The variable we found this applies to in our particular game is used for player health and is not used to index an array or otherwise manipulate any pointers.
It might be used for the width of a rect for IDISPLAY_FillRect(), ie: the health bar-- in which perhaps this means the device fails on FillRect() with negative widths. It was also being used in conjunction with FDIV().
This didnt cause any errors on 15 other handsets, just the KX2, so its definately a device issue no matter what the particular.
I think on some handsets when IDISPLAY_FillRect or IGRAPHIC_DrawRect with negative widths, it will cause power cycle.

keless wrote:The variable we found this applies to in our particular game is used for player health and is not used to index an array or otherwise manipulate any pointers.
It might be used for the width of a rect for IDISPLAY_FillRect(), ie: the health bar-- in which perhaps this means the device fails on FillRect() with negative widths. It was also being used in conjunction with FDIV().
This didnt cause any errors on 15 other handsets, just the KX2, so its definately a device issue no matter what the particular.
I think on some handsets when IDISPLAY_FillRect or IGRAPHIC_DrawRect with negative widths, it will cause power cycle.