[sjh]

How do people here debug stand-alone apps? I have an app that is a whole tree of files, so running it as a script is out. I build and run it as a sis, but when it dies I don't get to see the stack trace. Is there some trick to turn on the ability to see errors from the python interpreter?

-Seth

[jethro.fn]

To mimick a stack trace of the Python Script Shell, enclose your stand-alone program in a construct similar to this:

# Exception harness for "Python for S60" stand-alone programs

try:
    # Actual program is here.
    1 / 0
except:
    import sys
    import traceback
    import e32
    import appuifw
    appuifw.app.screen = "normal"               # Restore screen to normal size.
    appuifw.app.focus = None                    # Disable focus callback.
    body = appuifw.Text()
    appuifw.app.body = body                     # Create and use a text control.
    exitlock = e32.Ao_lock()
    def exithandler(): exitlock.signal()
    appuifw.app.exit_key_handler = exithandler  # Override softkey handler.
    appuifw.app.menu = [(u"Exit", exithandler)] # Override application menu.
    body.set(unicode("\n".join(traceback.format_exception(*sys.exc_info()))))
    exitlock.wait()                             # Wait for exit key press.
    appuifw.app.set_exit()

[simo.salminen]

One option is to use file logger utility, see this post for details: http://discussion.forum.nokia.com/fo...57&postcount=3

[tote_b5]

I have a slightly different problem: my PyS60 stand-alone app doesn't start at all. The application was assembled using Ensymble and it contains Python scripts as well as embedded SIS files. I've just added logging support to it and I'm afraid it's just that that causes it to malfunction.

Since logging does not work I cannot debug it. Now how shall I interpret jethro.fn's sentence: "...enclose your stand-alone program in a construct similar to this"? What to enclose? My stand-alone app naturally contains a default.py file, but it contains other files, too. Again, what to enclose? And am I right when I assume that I'll be unable to see any output? In which application's context would it be displayed (mine is crashing)?

Thanks,

Tote

[bogdan.galiceanu]

Technically you should put the exception harness around the code in your main .py file (the one that is used to create the sis file using Ensymble's py2sis) if you have just one such file. At least I think so...

And if you haven't already, see this article. It might help a bit.

[gaba88]

Originally Posted by tote_b5

I have a slightly different problem: my PyS60 stand-alone app doesn't start at all. The application was assembled using Ensymble and it contains Python scripts as well as embedded SIS files. I've just added logging support to it and I'm afraid it's just that that causes it to malfunction.

Since logging does not work I cannot debug it. Now how shall I interpret jethro.fn's sentence: "...enclose your stand-alone program in a construct similar to this"? What to enclose? My stand-alone app naturally contains a default.py file, but it contains other files, too. Again, what to enclose? And am I right when I assume that I'll be unable to see any output? In which application's context would it be displayed (mine is crashing)?

Thanks,

Tote

hi everybody
the method suggested by jethro.fn is a nice one and the best way which work for me is the exception harness method which is best ported in the wiki
have a look at that

[JOM]

Originally Posted by sjh

How do people here debug stand-alone apps? I have an app that is a whole tree of files, so running it as a script is out. I build and run it as a sis, but when it dies I don't get to see the stack trace. Is there some trick to turn on the ability to see errors from the python interpreter?

I have used tracing on hardware. Creates a huge log file, but it's worth the trouble. As an example of how to enable tracing, please download my Random Test and look inside. It's not too long and code should be pretty self-documenting.

I'll rewrite it later,

--jouni

[tote_b5]

Okay, I spotted it! I used multi-line comments (triple apostrophes/quotes) at the beginning of a function and that confused everything. After removing it (and only that part!) my program now works.

The thing is that I couldn't debug it at all in the traditional way: couldn't show a dialog, write anything to file, nothing. The biggest problem was that my program went crazy at the very beginning of the execution, I guess there must be a validator somewhere "who" decides if a Python script is syntactically correct or not. Mine wasn't.

So everybody, please learn from my mistake! I would be happier if I hadn't wasted couple of hours struggling to find this pity error.

Cheers,

Tote

[JOM]

Originally Posted by tote_b5

The thing is that I couldn't debug it at all in the traditional way: couldn't show a dialog, write anything to file, nothing. The biggest problem was that my program went crazy at the very beginning of the execution, I guess there must be a validator somewhere "who" decides if a Python script is syntactically correct or not.

That's called Static Code Analysis, one of my favorites

Short version:

- Install python 2.5
- Install pylint
- Run pylint on command line to check your PyS60 script
- Fix the errors and warnings, I mean really do it
- Redefine rule set by first writing defaults on file and then editing that

I'll write tutorial one of these days, but I'm using it and it works.

Cheers,

--jouni

[tote_b5]

Originally Posted by JOM

That's called Static Code Analysis, one of my favorites

Short version:

- Install python 2.5
- Install pylint
- Run pylint on command line to check your PyS60 script
- Fix the errors and warnings, I mean really do it
- Redefine rule set by first writing defaults on file and then editing that

I'll write tutorial one of these days, but I'm using it and it works.

Cheers,

--jouni

Looking forward to the tutorial, Jouni! And thanks for the tip, I will check it out soon!

Btw, is the following URL for pylint correct: http://www.logilab.org/857 ?

Tote

[JOM]

Originally Posted by tote_b5

Btw, is the following URL for pylint correct: http://www.logilab.org/857 ?

Seems to be, don't forget to install the dependencies first. Easy install didn't work for me, had to do it all manually.

Good luck,

--jouni

[Sean94]

I debug using appuifw.query.
sys.stderr=lambda x: appuifw.query(x, "query")

[GameDude]

I just checked in my serial logging tool, LogMan. Check it out from:
http://code.google.com/p/logman-for-symbian/

Announcement is here.

LogMan is a logging service running on Symbian phone intended for debugging tasks. The service allows one to send messages through a USB serial connection to PC. Other serial connection methods should work also, but are not supported. Infrared(IrComm), for example. On Symbian simulator, the messages are also logged to %TEMP%\epocwind.out by using RDebug logger.

How to use 'print' with LogMan.
===============================

import sys, pylogman
l = pylogman.LogMan()
l.Connect()
# Replace standard output with LogMan's write method.
sys.stdout.write = l.write

print "Hello!" # 'Hello' is sent to PC

Exceptions are sent automatically to PC and all debug logging is shown in real-time... which is quite nice