On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote:
I'll send you two screenshots offlist. Please feel
free to forward them to interested persons, just didn't
want to publish my path at the list.
20090428_pdbtrack3.png displays pdbtrack opened second
windows, cursor displayed at line 4 "import
Barry Warsaw wrote:
> On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote:
>
>> I'll send you two screenshots offlist. Please feel
>> free to forward them to interested persons, just didn't
>> want to publish my path at the list.
>>
>> 20090428_pdbtrack3.png displays pdbtrack opened second
>> wind
On May 1, 2009, at 4:50 PM, Andreas Roehler wrote:
Hhm. Could you give me an example, how you run script activating
pdbtrace, reaching
the standard (pdb) prompt from Emacs?
I almost always just add the following line to the source code at the
point I want to start debugging:
import p
On Fri, May 1, 2009 at 4:50 PM, Andreas Roehler
wrote:
> Barry Warsaw wrote:
> > On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote:
> >
> >> I'll send you two screenshots offlist. Please feel
> >> free to forward them to interested persons, just didn't
> >> want to publish my path at the list.
>
looking at this a little bit more closely, it's surprising to me not that it
fails for you, but that it works at all. have you made any changes to the
py-pdbtrack-input-prompt variable (aka 'python-pdbtrack-input-prompt' in
recent versions of python.el)?
as the docstring for py-pdbtrack-track-sta
ken manheimer wrote:
> looking at this a little bit more closely, it's surprising to me not
> that it fails for you, but that it works at all.
Hi Ken,
thats the point probably.
Originally question was: must we change the source-code in order to
make pdbtrack working, must we put a pdb.set_tra
