Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Jul 1998 09:44:07 +0200
From:      Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
To:        Stefan Eggers <seggers@semyam.dinoco.de>
Cc:        Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>, freebsd-hackers@FreeBSD.ORG
Subject:   Re: trace/KTRACE
Message-ID:  <19980704094407.07445@gil.physik.rwth-aachen.de>
In-Reply-To: <199807032042.WAA02287@semyam.dinoco.de>; from Stefan Eggers on Fri, Jul 03, 1998 at 10:42:50PM %2B0200
References:  <199807030924.LAA20365@gilberto.physik.RWTH-Aachen.DE> <199807032042.WAA02287@semyam.dinoco.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 03, 1998 at 10:42:50PM +0200, Stefan Eggers wrote:
> > I would like to find out where an application 'hangs' for
> > some overly long time (possibly a network/socket call or something)
> 
> > The problem using the kernel option KTRACE would be
> > that I cannot watch the application as it performs, instead I can
> > only trace 'a posteriori'.
> 
> So you'd like to have the ktrace output right when the call gets done
> instead of seeing the whole log after the show ended?  How about using
> option -l of kdump then?

Thanks. That could be a solution as well although I like the presence
of 'truss' now that I've learnt it's there.

> 
> It works in 2.2-stable - just tried it with xcalc.  I saw the system
> calls when they were done instead of having to go through the log
> afterwards.
> 
> If you want to avoid extremly large files with the ktrace output you
> might redirect it to /dev/stdout, pipe that into kdump and tell kdump
> to read from /dev/stdin.  I didn't test it and it might fail but is
> worth a try.
> 
> Stefan.
> -- 
> Stefan Eggers                 Lu4 yao2 zhi1 ma3 li4,
> Max-Slevogt-Str. 1            ri4 jiu3 jian4 ren2 xin1.
> 51109 Koeln
> Federal Republic of Germany

-- 
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980704094407.07445>