Also crash - Undef Inst Exception 0xde885cf0 | developer.brewmp.com Also crash - Undef Inst Exception 0xde885cf0 | developer.brewmp.com

Developer

Also crash - Undef Inst Exception 0xde885cf0

Forums:

after i have burn my app up to the phone, i start it, then it crashes. so bad with the hint below: Undef Inst Exception 0xde885cf0

more seriously, the handset crashes as well, without any response to any pressed key. :(

did someone else come with the same problem?
i'm so frustrated :(

Try deleting the application from the phone, power cycle and copy the application again.
ruben

Try deleting the application from the phone, power cycle and copy the application again.
ruben

hi, ruben.
the problem's so serious that after i delete it and re-burn my app, the cellphone still crashes, with the error code in the same format. just the 0x******** changed. what's wrong with it??
michael

hi, ruben.
the problem's so serious that after i delete it and re-burn my app, the cellphone still crashes, with the error code in the same format. just the 0x******** changed. what's wrong with it??
michael

the reason of crash can be some resourse file you are using is missing, also if you are creating an instance and it fails then also your app may crash....
sdg

the reason of crash can be some resourse file you are using is missing, also if you are creating an instance and it fails then also your app may crash....
sdg

Try using DBGPRINTFs (if supported on the handset) to find out where it crashes.
Does the application work fine on the emulator? Have you loaded the resource and sig files?

Try using DBGPRINTFs (if supported on the handset) to find out where it crashes.
Does the application work fine on the emulator? Have you loaded the resource and sig files?

Are you using a big endian/little endian compilation when you shouldn't be?

Are you using a big endian/little endian compilation when you shouldn't be?

I have also encountered similar strange problem.
For example, one of my application works perfectly, didn't have any crash problem as I used/tested this application for months. Then couple of weeks back, when I recompiled the code and downloaded the app, and I saw similar problem. I shut down the phone and then redownload the application and then it worked. I guess there might be some problem with apploader which causes this.
ruben

I have also encountered similar strange problem.
For example, one of my application works perfectly, didn't have any crash problem as I used/tested this application for months. Then couple of weeks back, when I recompiled the code and downloaded the app, and I saw similar problem. I shut down the phone and then redownload the application and then it worked. I guess there might be some problem with apploader which causes this.
ruben

Sometimes Apploader file transfers will be corrupted, but it's very rare. If you notice that the file written to the phone has an incorrect size, you should try reloading it.

Sometimes Apploader file transfers will be corrupted, but it's very rare. If you notice that the file written to the phone has an incorrect size, you should try reloading it.

hi, all.
first, my app works perfectly on the emulator, but crashes on the phone.
after the crashes, i modified my source code, i wiped off all the lines with the IMedia interface, and tried again. then, it worked. i think it might be that the brew envirenment on this phone is special, may be its hardware cannot well support the IMedia interface. maybe it's not the apploader's business ;-)
BTW, how to use DBGPRINTFs on the phone, someone can give a tip?
-michael

hi, all.
first, my app works perfectly on the emulator, but crashes on the phone.
after the crashes, i modified my source code, i wiped off all the lines with the IMedia interface, and tried again. then, it worked. i think it might be that the brew envirenment on this phone is special, may be its hardware cannot well support the IMedia interface. maybe it's not the apploader's business ;-)
BTW, how to use DBGPRINTFs on the phone, someone can give a tip?
-michael

use
DBGPRINTF(" type message here");
at point where you want to check the status of app...
u have to use applogger to view the output from it....
check applogger help for more.....
sdg

use
DBGPRINTF(" type message here");
at point where you want to check the status of app...
u have to use applogger to view the output from it....
check applogger help for more.....
sdg

Is this a BREW 2.0 phone, or were you using the 2.0 SDK to write applications for a 1.x phone?

Is this a BREW 2.0 phone, or were you using the 2.0 SDK to write applications for a 1.x phone?

hi michael...
is your app crashing after running.... or without....
if it is crashing after running then you have memory leak problem / or it is due to watchdog timer (if it is running for longer duration)...
and if it is crashing without even starting then there may be missing resourse file.....
specify your problem clearly....
sdg

hi michael...
is your app crashing after running.... or without....
if it is crashing after running then you have memory leak problem / or it is due to watchdog timer (if it is running for longer duration)...
and if it is crashing without even starting then there may be missing resourse file.....
specify your problem clearly....
sdg

hi, mohlendo:
the handset is designed for brew 2.0.1, i have asked the manufacture provider, they said that as a result of the restriction of the hardware, only "*.mmf" file is supported when using the IMedia interface, but my file are all *.qcp, so it crashes.
then, sdg:
i'll try the debugger with the applogger, i've never used it.
and i think it must be crashed with the IMedia interface initialization, because my media is initialized in the _InitAppData(...), so crashes with the app starts.
-michael

hi, mohlendo:
the handset is designed for brew 2.0.1, i have asked the manufacture provider, they said that as a result of the restriction of the hardware, only "*.mmf" file is supported when using the IMedia interface, but my file are all *.qcp, so it crashes.
then, sdg:
i'll try the debugger with the applogger, i've never used it.
and i think it must be crashed with the IMedia interface initialization, because my media is initialized in the _InitAppData(...), so crashes with the app starts.
-michael

hi...
which handset you are using....
i believe that all MSM chipsets supports qcp...
sdg

hi...
which handset you are using....
i believe that all MSM chipsets supports qcp...
sdg

:p its a very boring phone that has not come to the market. they said the the CPU's performance is limited and you'd better not use the *.qcp. :mad:
-michael

:p its a very boring phone that has not come to the market. they said the the CPU's performance is limited and you'd better not use the *.qcp. :mad:
-michael

are you looking in correct forum.... this is for BREW developers...
by the way what is name of that boring phoen... i think it will never come in market with a BREW tag....
sdg

are you looking in correct forum.... this is for BREW developers...
by the way what is name of that boring phoen... i think it will never come in market with a BREW tag....
sdg