diff options
author | Christian Tismer <tismer@stackless.com> | 2002-05-28 08:04:00 (GMT) |
---|---|---|
committer | Christian Tismer <tismer@stackless.com> | 2002-05-28 08:04:00 (GMT) |
commit | 313a7513b0c5771042d850d70782a2448d1cdcb7 (patch) | |
tree | c6ef8a458900ef778d90da931b769aaa35fe7dbb /Python/dynload_hpux.c | |
parent | 72de9c7a9c06bfe498c04ef134f510c51a5aef98 (diff) | |
download | cpython-313a7513b0c5771042d850d70782a2448d1cdcb7.zip cpython-313a7513b0c5771042d850d70782a2448d1cdcb7.tar.gz cpython-313a7513b0c5771042d850d70782a2448d1cdcb7.tar.bz2 |
This is a Python 2.1 and 2.2 bugfix candidate:
(or how do I "mark" something to be a candidate?)
fixed an old buglet that caused bdb to be unable to
continue in the botframe, after a breakpoint was set.
the key idea is not to set botframe to the bottom level frame,
but its f_back, which actually might be None.
Additional changes: migrated old exception trick to use
sys._getframe(), which exists both in 2.1 and 2.2 .
Note: I believe Mark Hammond needs to look over his code now.
F5 correctly starts up in the debugger, but later on doesn't stop at a given
breakpoint any longer.
kind regards - chris
Diffstat (limited to 'Python/dynload_hpux.c')
0 files changed, 0 insertions, 0 deletions