Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Pdb "commands" command with no bpnumber should use last available breakpoint #142834

Closed
Labels
stdlibStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or error
@cocolato

Description

@cocolato

Bug report

Bug description:

According to thedocumentation:

With no bpnumber argument, commands refers to the last breakpoint set.

I think the intended meaning should be the last available breakpoint. However, when using thecommands command without specifying a breakpoint number, if the most recently created breakpoint has been deleted, the current behavior throws an error stating "Breakpoint N already deleted".

main.py:

foo=1bar=2
➜ ./python-mpdbmain.py>/cpython/main.py(2)<module>()->foo=1(Pdb)b3Breakpoint1at/cpython/main.py:3(Pdb)b2Breakpoint2at/cpython/main.py:2(Pdb)clear2Deletedbreakpoint2at/cpython/main.py:2(Pdb)commands# should set command on breakpoint 1***cannotsetcommands:Breakpoint2alreadydeleted

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    stdlibStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2026 Movatter.jp