pdb

问题 I am using apollocaffe and Reinspect. Apollocaffe is in c++ library and Reinspect is in python. Reinspect called apis from apollocaffe. I like to debug those apis inside apollocaffe. From python code, I used python -m pdb train.py But I can't go inside api from apollocaffe. I do like cout << "test" << endl; in apollocaffe . But nothing is printed to console. How can I debug c++ code, at least if I can print, it will be great. 回答1: If you are interested to debug just the C++ part, you can just

问题 I am using apollocaffe and Reinspect. Apollocaffe is in c++ library and Reinspect is in python. Reinspect called apis from apollocaffe. I like to debug those apis inside apollocaffe. From python code, I used python -m pdb train.py But I can't go inside api from apollocaffe. I do like cout << "test" << endl; in apollocaffe . But nothing is printed to console. How can I debug c++ code, at least if I can print, it will be great. 回答1: If you are interested to debug just the C++ part, you can just

问题 I am using apollocaffe and Reinspect. Apollocaffe is in c++ library and Reinspect is in python. Reinspect called apis from apollocaffe. I like to debug those apis inside apollocaffe. From python code, I used python -m pdb train.py But I can't go inside api from apollocaffe. I do like cout << "test" << endl; in apollocaffe . But nothing is printed to console. How can I debug c++ code, at least if I can print, it will be great. 回答1: If you are interested to debug just the C++ part, you can just

问题 nosetests --pdb let's me halt upon error or failure, but this is too late for my needs. Stepping through code during execution helps me debug where the problem is. However, nosetests are helpful as they allow tests that rely on relative imports (i.e. tests in a package). How can I set breakpoints before the tests are executed? Currently I'm using: python -m pdb /path/to/my/nosetests testfile.py This solution isn't adequate. Nosetests interfere with pdb output, and my keyboard controls (e.g.

问题 nosetests --pdb let's me halt upon error or failure, but this is too late for my needs. Stepping through code during execution helps me debug where the problem is. However, nosetests are helpful as they allow tests that rely on relative imports (i.e. tests in a package). How can I set breakpoints before the tests are executed? Currently I'm using: python -m pdb /path/to/my/nosetests testfile.py This solution isn't adequate. Nosetests interfere with pdb output, and my keyboard controls (e.g.

问题 nosetests --pdb let's me halt upon error or failure, but this is too late for my needs. Stepping through code during execution helps me debug where the problem is. However, nosetests are helpful as they allow tests that rely on relative imports (i.e. tests in a package). How can I set breakpoints before the tests are executed? Currently I'm using: python -m pdb /path/to/my/nosetests testfile.py This solution isn't adequate. Nosetests interfere with pdb output, and my keyboard controls (e.g.

问题 nosetests --pdb let's me halt upon error or failure, but this is too late for my needs. Stepping through code during execution helps me debug where the problem is. However, nosetests are helpful as they allow tests that rely on relative imports (i.e. tests in a package). How can I set breakpoints before the tests are executed? Currently I'm using: python -m pdb /path/to/my/nosetests testfile.py This solution isn't adequate. Nosetests interfere with pdb output, and my keyboard controls (e.g.

来源： https://stackoverflow.com/questions/46169522/how-to-debug-underlying-c-library-from-python-interface

来源： https://stackoverflow.com/questions/54863123/how-to-print-call-stack-with-argument-values

来源： https://stackoverflow.com/questions/54863123/how-to-print-call-stack-with-argument-values