From owner-freebsd-hackers Fri Jul 3 03:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27414 for freebsd-hackers-outgoing; Fri, 3 Jul 1998 03:05:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27404 for ; Fri, 3 Jul 1998 03:05:01 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id DAA14450 for ; Fri, 3 Jul 1998 03:03:38 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id LAA20365 for freebsd-hackers@freefall.cdrom.com; Fri, 3 Jul 1998 11:24:53 +0200 (MEST) (envelope-from kuku) Date: Fri, 3 Jul 1998 11:24:53 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807030924.LAA20365@gilberto.physik.RWTH-Aachen.DE> To: freebsd-hackers@freefall.cdrom.com Subject: trace/KTRACE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to find out where an application 'hangs' for some overly long time (possibly a network/socket call or something) Recently I grabbed out 'trace-1.6' for a HP-UX machine which is supposed to be based on the SUN kernel trace interface. 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'. Would the be a way to support this utility and the kernel trace interface under FreeBSD? Or are there any other ways (other than profiling, which is also an a posteriori method) to 'watch' what an app does? -- 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