Debugging confusion -- too many stacks!
Christian Tismer
tismer at tismer.com
Sun Apr 2 12:33:58 EDT 2000
Darrell wrote:
>
> From: "Christian Tismer"
> > The following watches are always active when I'm debuging:
> > (are there similar ways to do this with PDB?)
> >
> > (char*)(f->f_code->co_name)+20 # current function name
> > (char*)(f->f_code->co_filename)+20 # current file name
> > f->f_lineno # line number
> >
> > In order to see which frame is calling you, do the same, but
> > replace "f" by "f->f_back".
>
> pdb works pretty good.
> I use it all the time. You can get the call stack or what ever you want to
> look at.
Oops, sorry! I confused PDB with GDB.
Probably since the issue was about stacks...
ciao - chris
--
Christian Tismer :^) <mailto:tismer at appliedbiometrics.com>
Applied Biometrics GmbH : Have a break! Take a ride on Python's
Kaunstr. 26 : *Starship* http://starship.python.net
14163 Berlin : PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF
we're tired of banana software - shipped green, ripens at home
More information about the Python-list
mailing list