This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients xdegaye
Date 2012-06-19.15:50:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340121053.81.0.484890828035.issue14913@psf.upfronthosting.co.za>
In-reply-to
Content
Uploaded pdb_default_2.patch.
This new patch fixes the previous patch that fails to stop at
breakpoints set in nested functions, and extends the previous patch in
allowing breakpoints outside function and method definitions.

> When a breakpoint is set at the line number of a function definition,
> the algorithm used to find the first statement of the function (the
> actual breakpoint) is not robust, so that when another breakpoint is
> also set at this fuction using the function name instead of the line
> number, then this last breakpoint hides the first one.

This is not correct. One should read instead:

    When a breakpoint is set at the first statement of a function and
    another breakpoint is set using the function name, then the first
    breakpoint hides the other one.

This is fixed as well in both patches.
History
Date User Action Args
2012-06-19 15:50:54xdegayesetrecipients: + xdegaye
2012-06-19 15:50:53xdegayesetmessageid: <1340121053.81.0.484890828035.issue14913@psf.upfronthosting.co.za>
2012-06-19 15:50:53xdegayelinkissue14913 messages
2012-06-19 15:50:53xdegayecreate