Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Debugging a test

X-seq: zsh-users 6668
From: Mads Martin Joergensen <mmj@xxxxxxx>
To: Dominic Mitchell <dom@xxxxxxxxxxxxxxxx>
Subject: Re: Debugging a test
Date: Thu, 9 Oct 2003 14:50:44 +0200
Cc: zsh-users@xxxxxxxxxx
In-reply-to: <20031009122355.GA26014@xxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <20031009121008.GD28237@xxxxxxx> <20031009122355.GA26014@xxxxxxxxxxxxxxxxxxxx>

* Dominic Mitchell <dom@xxxxxxxxxxxxxxxx> [Oct 09. 2003 14:24]:
> > When running V01zmodload.ztst in an environment with a profiling enabled
> > gcc, zsh hangs burning 99.9% CPU. Adding an strace to the process gives
> > no output at all.
> > 
> > So I was wondering how to enable some kind of debug info to the module
> > in order to have it e.g. print how far it gets, in order to nail down
> > what causes the loop?
> 
> If you've got it installed, try ltrace instead of strace.

Same effect. Nothing happens, no output at all.

-- 
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                -- A. P. J.

Follow-Ups:
- Re: Debugging a test
  - From: Cosmo

References:
- Debugging a test
  - From: Mads Martin Joergensen
- Re: Debugging a test
  - From: Dominic Mitchell

Messages sorted by: Reverse Date, Date, Thread, Author