blocks|key|4261139|text|在更好地理解问题后进行更新：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4261140|一般来说，我不认为这是测试代码的理想方式；为可测试性设计代码(例如使用TDD)通常会导致更容易测试的函数(例如使用mock/fake对象、依赖注入等)，如果可能的话，我鼓励您考虑重构代码。这种方法的另一个问题是，测试可能会变得与代码紧密耦合。但是，我在这里假设您知道自己在做什么，并且无论出于什么原因，上面都不是一个选项。|4261141|脚本pdb|4261142|如果你想从代码中编写pdb脚本，实际上可以通过实例化你自己的pdb.Pdb类并在编写时传入stdin和stdout参数(我不确定两者是否都需要--我已经提交了https://bugs.python.org/issue33749)。|offset|length|style|CODE|4261143|示例(我只是在fun中添加了额外的输入参数)：|4261144|def+fun(i):
++++a+=+10+%2B+i
++++c+=+fun2(a)
++++d+=+40
++++return+c%2Bd
def+fun2(a):
++++xyz+='str'
++++return+a%2B10

import+pdb
import+io
output+=+io.StringIO()
#+this+contains+the+pdb+commands+we+want+to+execute:
pdb_script+=+io.StringIO("p+i;;+i+=+100;;+n;;+p+a;;+c;;")
mypdb+=+pdb.Pdb(stdin=pdb_script,+stdout=output)|code-block|syntax|javascript|4261145|正常结果(无脚本)：|4261146|In+[40]:+pdb.runcall(fun,+1)
++++...:
>+<ipython-input-1-28966c4f6e38>(2)fun()
->+a+=+10+%2B+i
(Pdb)
(Pdb)+c
Out[40]:+61|4261147|脚本化pdb：|4261148|In+[44]:+mypdb+=+pdb.Pdb(stdin=pdb_script,+stdout=output)

In+[45]:+mypdb.runcall(fun,+1)
Out[45]:+160

In+[50]:+print(output.getvalue())
>+<ipython-input-1-28966c4f6e38>(2)fun()
->+a+=+10+%2B+i
(Pdb)+1
>+<ipython-input-1-28966c4f6e38>(3)fun()
->+c+=+fun2(a)
110|4261149|您可能会发现使用pdb_script.seek(0)重置脚本很有帮助。|4261150|原始答案-使用条件断点|4261151|听起来您真正想要的是只有在代码处于特定状态时才进入调试器。这可以通过条件断点来实现(详细信息请参见pdb+docs+)。例如，假设您想在a+>+10的情况下中断fun2|4261152|+++...:

In+[2]:+import+pdb

In+[3]:+pdb.runcall(fun,+1)
>+<ipython-input-1-28966c4f6e38>(2)fun()
->+a+=+10+%2B+i
(Pdb)+break+fun2,+a+>+10
Breakpoint+1+at+<ipython-input-1-28966c4f6e38>:6
(Pdb)+c
>+<ipython-input-1-28966c4f6e38>(7)fun2()
->+xyz+='str'
(Pdb)+c
Out[3]:+61

In+[4]:+pdb.runcall(fun,+-1)
>+<ipython-input-1-28966c4f6e38>(2)fun()
->+a+=+10+%2B+i
(Pdb)+c
Out[4]:+59|4261153|请注意，在第一种情况下，您命中了断点，在第二种情况下，您没有命中断点。|4261154|原始答案-使用断点并在命中时执行命令|4261155|您还可以尝试设置断点并使用commands工具。|4261156|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.python.org/issue33749|1|https://docs.python.org/3/library/pdb.html|2|https://docs.python.org/3/library/pdb.html#pdbcommand-commands^0|0|0|0|U|7|19|5|1F|6|27|Y|0|0|7|3|0|0|0|0|0|0|8|I|0|0|1D|3|1W|6|28|4|1D|8|1|0|0|0|0|D|8|2|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1T|8|@$H|1U|I|1V|J|K]|$H|1W|I|1X|J|K]|$H|1Y|I|1Z|J|K]]|9|@$H|20|I|21|1|22]]|A|$]]|$1|L|3|M|5|6|7|23|8|@$H|24|I|25|J|K]]|9|@]|A|$]]|$1|N|3|O|5|P|7|26|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|27|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|28|8|@]|9|@]|A|$Q|R]]|$1|W|3|X|5|6|7|29|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|P|7|2A|8|@]|9|@]|A|$Q|R]]|$1|10|3|11|5|6|7|2B|8|@$H|2C|I|2D|J|K]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2E|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2F|8|@$H|2G|I|2H|J|K]|$H|2I|I|2J|J|K]|$H|2K|I|2L|J|K]]|9|@$H|2M|I|2N|1|2O]]|A|$]]|$1|16|3|17|5|P|7|2P|8|@]|9|@]|A|$Q|R]]|$1|18|3|19|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2S|8|@]|9|@$H|2T|I|2U|1|2V]]|A|$]]|$1|1E|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]]|1F|$1G|$5|1H|1I|1J|A|$1K|1L]]|1M|$5|1H|1I|1J|A|$1K|1N]]|1O|$5|1H|1I|1J|A|$1K|1P]]]]

<p>Update after better understanding the question:</p>

<p>In general, I don't think this is the ideal way to test code; designing code for testability (e.g. using TDD) will often result in functions that are easier to test (e.g. using mocks/fake objects, dependency injection etc), and I would encourage you to consider refactoring the code if possible. The other issue with this approach is that the tests may become very tightly coupled to the code. However, I'll assume here that you know what you are doing, and that the above is not an option for whatever reason.</p>

<h2>Scripting pdb</h2>

<p>If you want to script pdb from code, this is actually possible by instantiating your own <code>pdb.Pdb</code> class and passing in the <code>stdin</code> and, at the time of writing, <code>stdout</code> argument (I'm not sure both should be required - I've filed <a href="https://bugs.python.org/issue33749" rel="nofollow noreferrer">https://bugs.python.org/issue33749</a>).</p>

<p>Example (I just added the extra input argument to <code>fun</code>):</p>

<pre><code>def fun(i):
    a = 10 + i
    c = fun2(a)
    d = 40
    return c+d
def fun2(a):
    xyz ='str'
    return a+10

import pdb
import io
output = io.StringIO()
# this contains the pdb commands we want to execute:
pdb_script = io.StringIO("p i;; i = 100;; n;; p a;; c;;")
mypdb = pdb.Pdb(stdin=pdb_script, stdout=output)
</code></pre>

<p>Normal result (no scripting):</p>

<pre><code>In [40]: pdb.runcall(fun, 1)
    ...:
&gt; &lt;ipython-input-1-28966c4f6e38&gt;(2)fun()
-&gt; a = 10 + i
(Pdb)
(Pdb) c
Out[40]: 61
</code></pre>

<p>Scripted pdb:</p>

<pre><code>In [44]: mypdb = pdb.Pdb(stdin=pdb_script, stdout=output)

In [45]: mypdb.runcall(fun, 1)
Out[45]: 160

In [50]: print(output.getvalue())
&gt; &lt;ipython-input-1-28966c4f6e38&gt;(2)fun()
-&gt; a = 10 + i
(Pdb) 1
&gt; &lt;ipython-input-1-28966c4f6e38&gt;(3)fun()
-&gt; c = fun2(a)
110
</code></pre>

<p>You may find using <code>pdb_script.seek(0)</code> helpful to reset the script.</p>

<h2>Original answer - using conditional breakpoints</h2>

<p>It sounds like what you really want is to only get into the debugger when your code is in a certain state. This can be done with conditional breakpoints (see <a href="https://docs.python.org/3/library/pdb.html" rel="nofollow noreferrer"><code>pdb</code> docs</a> for details).
For example, let's say you want to break in <code>fun2</code> if <code>a &gt; 10</code>:</p>

<pre><code>   ...:

In [2]: import pdb

In [3]: pdb.runcall(fun, 1)
&gt; &lt;ipython-input-1-28966c4f6e38&gt;(2)fun()
-&gt; a = 10 + i
(Pdb) break fun2, a &gt; 10
Breakpoint 1 at &lt;ipython-input-1-28966c4f6e38&gt;:6
(Pdb) c
&gt; &lt;ipython-input-1-28966c4f6e38&gt;(7)fun2()
-&gt; xyz ='str'
(Pdb) c
Out[3]: 61

In [4]: pdb.runcall(fun, -1)
&gt; &lt;ipython-input-1-28966c4f6e38&gt;(2)fun()
-&gt; a = 10 + i
(Pdb) c
Out[4]: 59
</code></pre>

<p>Notice in the first case you hit the breakpoint, in the second you didn't.</p>

<h2>Original answer - using breakpoints and executing commands when hit</h2>

<p>You could also try setting a breakpoint and using the <a href="https://docs.python.org/3/library/pdb.html#pdbcommand-commands" rel="nofollow noreferrer">commands</a> facility.</p>


<p>I am calling pdb on some function <code>func</code> i.e.,</p>

<pre><code>def fun():
    a = 10
    c = fun2(a)
    d = 40
    return c+d
def fun2(a):
    xyz ='str'
    return a+10
</code></pre>

<p>Now I am running pdb using <code>pdb.runcall(func,a,b)</code> now It will open a pdb console for debugging, now suppose I press 2 time <code>s</code>(step) and <code>q</code> to <code>quit</code> in <code>pdb</code> console
but problem is I don't want to do this manually, I want to make some script  which do something like this (automatic tell pdb first two command is <code>s</code> then third is <code>q</code>) , I am asking because there are many functions which needs atleast two time <code>c</code> (continue) to overall excecution of function so that it can yield/return some valid output (like say generators)</p>

<p>Any help will be a serious help for me.</p>


How to automate pdb commands?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在某个函数func上调用pdb，即，def fun():    a = 10    c = fun2(a)    d = 40    return c+ddef fun2(a):    xyz ='str'    return a+10现在我正在使用pdb.runcall(func,a,b)运行pdb，它将打开pdb...

如何自动执行pdb命令？-腾讯云开发者社区-腾讯云

问如何自动执行pdb命令？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何自动执行pdb命令？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何自动执行pdb命令？
EN