On Mon, Feb 4, 2013 at 8:41 AM, Johann Spies <[email protected]> wrote: > Hallo Mariano, > >> >> Can you send us a minimal example to reproduce this issue? >> > > > I have tried to get a minimal example but when I create a new app and test > it there it works and I could not reproduce the problem. However I cannot > get it to work on my other app which is not that minimal.
Any factor that you can distinguish between them? Just to be sure, are you trying this in development (with rocket webserver), right? > I get inconsistent results. Sometimes I get the same as that about which I > have asked my original question. Sometimes the breakpoint is totally > ignored. At one stage I had to force kill web2py because nothing worked and > it would not end on a normal kill SIGTERM <pid>. Breakpoints should not be ignored, this can happen only if some library is messing up the internal python threading structures, or playing with the python interpreter (such profilers or test coverage tools that modify sys.settrace). Are you using any non-conventional tool? Maybe this could be a bug in the debugger infrastructure (bdb), could you try to reproduce using pdb to discard external issues? For example, the following command will open a pdb console: import pdb; pdb.set_trace() Then, you could use the python command to set breakpoints: http://docs.python.org/2/library/pdb.html The SIGTERM issue is a known bug (at least I can reproduce it most times). I think it is related to python threading and rocket, but I didn't investigated deep enough. It should not be a debugger problem, as standalone usage is working fine (SIGTERM is honoured) > Maybe the console message (which I have seen today for the first time) is > related: > > web2py Web Framework > Created by Massimo Di Pierro, Copyright 2007-2013 > Version 2.4.1-alpha.2+timestamp.2013.02.03.09.10.34 > Database drivers available: SQLite(sqlite2), SQLite(sqlite3), > MySQL(pymysql), PostgreSQL(psycopg2), PostgreSQL(pg8000), IMAP(imaplib) > please visit: > http://127.0.0.1:8000/ > use "kill -SIGTERM 3796" to shutdown the web2py server > Failed to setup thread-interrupt handler. This is usually not critical > *** DO_CLEAR failed Non-numeric breakpoint number (all}) > Certainly, the last messages are worthy. thread-interrupt could be related to the threading issues described early. DO_CLEAR is from the python bdb module, related to temp breakpoints. Could you tell me how reproduce them? (i.e., whose libraries are you using, how are you setting breakpoints, etc.) Best regards and thanks for your collaboration, Mariano Reingart http://www.sistemasagiles.com.ar http://reingart.blogspot.com -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
