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

Re: Debugging a test

X-seq: zsh-users 6669
From: Cosmo <cosmo@xxxxxxxxxx>
To: Mads Martin Joergensen <mmj@xxxxxxx>
Subject: Re: Debugging a test
Date: Thu, 09 Oct 2003 14:21:41 +0100
Cc: zsh-users@xxxxxxxxxx
In-reply-to: <20031009125044.GC25849@xxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
Organization: IBM Informix
References: <20031009121008.GD28237@xxxxxxx> <20031009122355.GA26014@xxxxxxxxxxxxxxxxxxxx> <20031009125044.GC25849@xxxxxxx>

Mads Martin Joergensen wrote:




* 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.


You're in a tight loop somewhere, not making any library or system calls.
Attach to the process with a debugger and get a stack trace.




Cosmo

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

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