pydb 1.21 is started with -T. When I type in "info threads", pydb throws the following exception and freezes. Can someone please help? I have Python 2.4.3 and threadframe.
Traceback (most recent call last):
File "../util/runapp.py", line 138, in runAppLinux
app.runReactorWithLogging(config, oldstdout, oldstderr)
File "/home/monsoon/lib/python2.4/site-packages/twisted/application/app.py", line 131, in runReactorWithLogging
reactor.run()
File "/home/monsoon/lib/python2.4/site-packages/twisted/internet/posixbase.py", line 218, in run
self.mainLoop()
File "/home/monsoon/lib/python2.4/site-packages/twisted/internet/posixbase.py", line 229, in mainLoop
self.doIteration(t)
--- <exception caught here> ---
File "/home/monsoon/lib/python2.4/site-packages/twisted/internet/selectreactor.py", line 97, in doSelect
[], timeout)
File "/home/monsoon/lib/python2.4/site-packages/pydb/gdb.py", line 232, in trace_dispatch_gdb
return self.trace_dispatch_old(frame, event, arg)
File "/home/monsoon/lib/python2.4/bdb.py", line 54, in trace_dispatch
return self.dispatch_exception(frame, arg)
File "/home/monsoon/lib/python2.4/bdb.py", line 91, in dispatch_exception
self.user_exception(frame, arg)
File "/home/monsoon/lib/python2.4/site-packages/pydb/pydbbdb.py", line 351, in user_exception
self.interaction(frame, exc_traceback)
File "/home/monsoon/lib/python2.4/site-packages/pydb/gdb.py", line 447, in interaction
self.cmdloop()
File "/home/monsoon/lib/python2.4/cmd.py", line 142, in cmdloop
stop = self.onecmd(line)
File "/home/monsoon/lib/python2.4/site-packages/pydb/pydbcmd.py", line 441, in onecmd
return cmd.Cmd.onecmd(self, line)
File "/home/monsoon/lib/python2.4/cmd.py", line 219, in onecmd
return func(arg)
File "/home/monsoon/lib/python2.4/site-packages/pydb/gdb.py", line 1315, in do_info
self.infocmds.do(self, args[0], args)
File "/home/monsoon/lib/python2.4/site-packages/pydb/subcmd.py", line 78, in do
entry['callback'](arg)
exceptions.TypeError: info_thread_old() takes at least 2 arguments (1 given)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm glad you were about to solve this problem. Still, it does reflect a bug in the pydb code, which I've just fixed in my local CVS copy. I can't check this back into CVS right now as my DSL line has been out for the last couple of days.
Covad Rant:
Covad knocked out my DSL line when their equipment failed in their central office. Who knows for how many other people; and estimate I got from my ISP was that it was about 100 people. They have to be told that they knocked out service, as they don't monitor their equipment and aren't all that forthcoming about information when they do; instead they seem to rely on your telling them their equipment failed indirectly via your ISP. Nor do they keep logs more than a couple of hours for persistent problems with customers. In over two days they haven't been able fix the outage they caused.
We are told (again via the ISP), well it's only "best effort" service anyway so basically they can do whatever they want. Covad's first line of defense is to schedule sending someone out to your home (rather than test their equipment, and it looks like they don't have much in the way of doing that either). This means being at home tied there for 4-8 hours; on one occasion they lied and said they showed up when they in didn't. The nice but incompetent Covad telephone tech has done as much or more damage to my home telephone service as he's done to fix problems. I'll probably be switching to cable, and it will also probably mean that I'll change ISPs as well. I guess it's a pity for the ISP - if a couple of ISP's have to die for Covad to die, so be it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
pydb 1.21 is started with -T. When I type in "info threads", pydb throws the following exception and freezes. Can someone please help? I have Python 2.4.3 and threadframe.
Traceback (most recent call last):
File "../util/runapp.py", line 138, in runAppLinux
app.runReactorWithLogging(config, oldstdout, oldstderr)
File "/home/monsoon/lib/python2.4/site-packages/twisted/application/app.py", line 131, in runReactorWithLogging
reactor.run()
File "/home/monsoon/lib/python2.4/site-packages/twisted/internet/posixbase.py", line 218, in run
self.mainLoop()
File "/home/monsoon/lib/python2.4/site-packages/twisted/internet/posixbase.py", line 229, in mainLoop
self.doIteration(t)
--- <exception caught here> ---
File "/home/monsoon/lib/python2.4/site-packages/twisted/internet/selectreactor.py", line 97, in doSelect
[], timeout)
File "/home/monsoon/lib/python2.4/site-packages/pydb/gdb.py", line 232, in trace_dispatch_gdb
return self.trace_dispatch_old(frame, event, arg)
File "/home/monsoon/lib/python2.4/bdb.py", line 54, in trace_dispatch
return self.dispatch_exception(frame, arg)
File "/home/monsoon/lib/python2.4/bdb.py", line 91, in dispatch_exception
self.user_exception(frame, arg)
File "/home/monsoon/lib/python2.4/site-packages/pydb/pydbbdb.py", line 351, in user_exception
self.interaction(frame, exc_traceback)
File "/home/monsoon/lib/python2.4/site-packages/pydb/gdb.py", line 447, in interaction
self.cmdloop()
File "/home/monsoon/lib/python2.4/cmd.py", line 142, in cmdloop
stop = self.onecmd(line)
File "/home/monsoon/lib/python2.4/site-packages/pydb/pydbcmd.py", line 441, in onecmd
return cmd.Cmd.onecmd(self, line)
File "/home/monsoon/lib/python2.4/cmd.py", line 219, in onecmd
return func(arg)
File "/home/monsoon/lib/python2.4/site-packages/pydb/gdb.py", line 1315, in do_info
self.infocmds.do(self, args[0], args)
File "/home/monsoon/lib/python2.4/site-packages/pydb/subcmd.py", line 78, in do
entry['callback'](arg)
exceptions.TypeError: info_thread_old() takes at least 2 arguments (1 given)
Please ignore my question. Turns out threadframe wasn't installed correctly.
I'm glad you were about to solve this problem. Still, it does reflect a bug in the pydb code, which I've just fixed in my local CVS copy. I can't check this back into CVS right now as my DSL line has been out for the last couple of days.
Covad Rant:
Covad knocked out my DSL line when their equipment failed in their central office. Who knows for how many other people; and estimate I got from my ISP was that it was about 100 people. They have to be told that they knocked out service, as they don't monitor their equipment and aren't all that forthcoming about information when they do; instead they seem to rely on your telling them their equipment failed indirectly via your ISP. Nor do they keep logs more than a couple of hours for persistent problems with customers. In over two days they haven't been able fix the outage they caused.
We are told (again via the ISP), well it's only "best effort" service anyway so basically they can do whatever they want. Covad's first line of defense is to schedule sending someone out to your home (rather than test their equipment, and it looks like they don't have much in the way of doing that either). This means being at home tied there for 4-8 hours; on one occasion they lied and said they showed up when they in didn't. The nice but incompetent Covad telephone tech has done as much or more damage to my home telephone service as he's done to fix problems. I'll probably be switching to cable, and it will also probably mean that I'll change ISPs as well. I guess it's a pity for the ISP - if a couple of ISP's have to die for Covad to die, so be it.