[pypy-dev] Re: type problems

[Michael Hudson]

holger krekel <hpk at trillke.net> writes:

> Hi Guenter,
>
> [G?nter Jantzen Wed, Jul 09, 2003 at 01:40:20PM +0200]
>> >
>> > Debugging PyPy is ludicrously complicated: I know Python as well as
>> > almost anyone.  I know more about PyPy than just a very few people.
>> > I'm fairly smart.  And *I* get hopelessly lost in the internals.  What
>> > can we do about this?
>> 
>> Hallo Michael,
>> 
>> sometimes when interactive debugging is complicated, it can be helpful to
>> avoid it and to use some kind of logging mechanism instead.
>
> That may be a good idea.  I am currently hunting down a deeply
> nested Exception problem and knowing which frames get created executing
> which code helps in understanding what's going on.  Without lots of
> print-statements this would be very difficult (not that it really gets
> easy :-).

I think the difficulty here might be trying to work out what to log.
You'd have to log *just the right amount* of information.

I guess it wouldn't be that hard to use a trace or profile function to
save a call tree, but then the problem becomes one of data
presentation and viusalization (I expect) -- and maybe memory consumption...

Cheers,
M.

-- 
  There are two kinds of large software systems: those that evolved
  from small systems and those that don't work.
                           -- Seen on slashdot.org, then quoted by amk