From owner-freebsd-hackers Sat Jul 4 00:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21114 for freebsd-hackers-outgoing; Sat, 4 Jul 1998 00:44:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21069 for ; Sat, 4 Jul 1998 00:44:01 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA26022; Sat, 4 Jul 1998 09:44:07 +0200 (MEST) (envelope-from kuku) Message-ID: <19980704094407.07445@gil.physik.rwth-aachen.de> Date: Sat, 4 Jul 1998 09:44:07 +0200 From: Christoph Kukulies To: Stefan Eggers Cc: Christoph Kukulies , freebsd-hackers@FreeBSD.ORG Subject: Re: trace/KTRACE References: <199807030924.LAA20365@gilberto.physik.RWTH-Aachen.DE> <199807032042.WAA02287@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199807032042.WAA02287@semyam.dinoco.de>; from Stefan Eggers on Fri, Jul 03, 1998 at 10:42:50PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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