Debugging a test

Debugging a test

[Mads Martin Joergensen]

Hello people,

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?

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

Re: Debugging a test

[Dominic Mitchell]

On Thu, Oct 09, 2003 at 02:10:08PM +0200, Mads Martin Joergensen wrote:
> Hello people,
> 
> 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.

-Dom

Re: Debugging a test

[Mads Martin Joergensen]

* Dominic Mitchell <dom@happygiraffe.net> [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.

Re: Debugging a test

[Cosmo]

Mads Martin Joergensen wrote:
> 
> 
> 
> * Dominic Mitchell <dom@happygiraffe.net> [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