[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pine-info
Subject:    Re: debugging pine
From:       Terry Gray <gray () cac ! washington ! edu>
Date:       2002-04-08 22:12:24
[Download RAW message or body]

See also:

 FEATURE: enable-mail-check-cue

-teg

On Mon, 8 Apr 2002, Jacob Morzinski wrote:

> On Mon, 8 Apr 2002, Joel Boonstra wrote:
> > How can I discover what exactly Pine is doing while it hangs, or slows
> > down?  I find that *very* frequently I wait for pine to do something.
>
> If you run pine with the "-d 9" command flag, you will get the highest
> level of debugging output.  The test that I did appeared to include
> timestamps for most logfile entries.  I don't know if you need "9" for
> the timestamps or if a less-verbose debuglevel would also give
> timestamps.
>
> The procedure I would follow would be to run pine with timestamps in
> the debug log, and compare the debug log of a "slow" pine against the
> debug log of a "fast" different pine.  	I don't expect it to be a
> miracle solution, but it may show you where to start examing the
> source or where to start debugging.
>
>


[prev in list] [next in list] [prev in thread] [next in thread]