Message170301
| Author |
brett.cannon |
| Recipients |
brett.cannon, eric.snow, exarkun |
| Date |
2012年09月11日.13:09:39 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1347368980.79.0.300695408958.issue15911@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I'm going to guess this is a shortcoming of pdb when it comes to frozen modules as I can get to the source using inspect (which pdb leans on)::
>>> len(inspect.findsource(_frozen_importlib)[0])
1761
>>> len(inspect.findsource(importlib._bootstrap)[0])
1761
Which are accurate line counts::
$ wc Lib/importlib/_bootstrap.py
1761 6236 62517 Lib/importlib/_bootstrap.py
So why gdb can't output the source line when it has the line number of the file I don't know when it can already get access to the source without issue.
And yes, debugging imports are hard. =) Still, it's better than before as you can easily toss in a print statement or two and then just regenerate the frozen object. But I do agree it would be nice to get gdb to play along with the whole situation (and thus the title change for this bug). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年09月11日 13:09:40 | brett.cannon | set | recipients:
+ brett.cannon, exarkun, eric.snow |
| 2012年09月11日 13:09:40 | brett.cannon | set | messageid: <1347368980.79.0.300695408958.issue15911@psf.upfronthosting.co.za> |
| 2012年09月11日 13:09:40 | brett.cannon | link | issue15911 messages |
| 2012年09月11日 13:09:39 | brett.cannon | create |
|