Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

how can I debug BREW Applet in VC60, such as set breakpoint?thanks!!

hi
just compile ur program shift+f7 or f7
then appley break point where ever u want f8
then press f5
u will need to give path of emulator exe file after f5
and the debuging start
Vaibhav

hi
just compile ur program shift+f7 or f7
then appley break point where ever u want f8
then press f5
u will need to give path of emulator exe file after f5
and the debuging start
Vaibhav

hi vaibhav
thank u for the answer, but when I run the application by F5 and set Brew emulator path, some promotion appears like follow:
"C:\program Files\brew sdk v2.01 zh\bin\brew_emulator.exe " does not contain debugging information. Press OK to continue.
and the break point will not be triggered.
what's wrong ?

hi vaibhav
thank u for the answer, but when I run the application by F5 and set Brew emulator path, some promotion appears like follow:
"C:\program Files\brew sdk v2.01 zh\bin\brew_emulator.exe " does not contain debugging information. Press OK to continue.
and the break point will not be triggered.
what's wrong ?

Oh, i got the problem, I forgot to set the work folder :)
Now, debuging is ok, thanks!

Oh, i got the problem, I forgot to set the work folder :)
Now, debuging is ok, thanks!

I meet same problem as yours. How to set work folder? Thanks!

I meet same problem as yours. How to set work folder? Thanks!

sorry, i had made a mistake that it's not related to setting the work floder.
You should move your "*.dll" from debug folder to the vc project folder. for example:
my application :
----MyApplication(floder)-|-- debug (floder)----MyApplication.dll(file)
| |--MyApplication.dsw(file)
|
|--MyApplication.mif
You should move "MyApplication.dll" to MyApplication Floder.

sorry, i had made a mistake that it's not related to setting the work floder.
You should move your "*.dll" from debug folder to the vc project folder. for example:
my application :
----MyApplication(floder)-|-- debug (floder)----MyApplication.dll(file)
| |--MyApplication.dsw(file)
|
|--MyApplication.mif
You should move "MyApplication.dll" to MyApplication Floder.

I think this error is back?
I cannot debug anything in VS 2003.
I have set the work dir to the be project dir as the previous poster suggested.
The .Dll is in the right place, not the /Debug folder so not sure where to move that.
I still get the ".. does not contain debugging information" message.
Can anyone point me in the right direction?
Thanks

I think this error is back?
I cannot debug anything in VS 2003.
I have set the work dir to the be project dir as the previous poster suggested.
The .Dll is in the right place, not the /Debug folder so not sure where to move that.
I still get the ".. does not contain debugging information" message.
Can anyone point me in the right direction?
Thanks

N/m
I just found this thread:
http://brewforums.qualcomm.com/showthread.php?t=7083&highlight=debugger
I haven't tried it but it looks like the .pdf there will fix my issue.

N/m
I just found this thread:
http://brewforums.qualcomm.com/showthread.php?t=7083&highlight=debugger
I haven't tried it but it looks like the .pdf there will fix my issue.

I really don't know if that's the best way but I use to place DBGPRINTF("someText") between code, generally between functions, then If it crashes before a certain DBGPRINTF it means that the bug is before it on some function sentence.. then you refine your DBGPRINTF between each function code line...
It is very easy to use and to be done, even so you can't debug your memory like looking deeply over it, but it is an useful tip.
Hope it helps.

I really don't know if that's the best way but I use to place DBGPRINTF("someText") between code, generally between functions, then If it crashes before a certain DBGPRINTF it means that the bug is before it on some function sentence.. then you refine your DBGPRINTF between each function code line...
It is very easy to use and to be done, even so you can't debug your memory like looking deeply over it, but it is an useful tip.
Hope it helps.