Date: Fri, 3 Jul 1998 08:02:06 -0400 (EDT) From: Nathan Dorfman <nathan@rtfm.net> To: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-hackers@FreeBSD.ORG Subject: Re: trace/KTRACE Message-ID: <199807031202.IAA02018@limbo.rtfm.net> In-Reply-To: <199807030924.LAA20365@gilberto.physik.RWTH-Aachen.DE>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199807030924.LAA20365@gilberto.physik.RWTH-Aachen.DE> you write: > >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? Compile it with debugging symbols and run gdb? >-- >Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de -- ________________ ___________________________________________ / Nathan Dorfman \ / "My problems start when the smarter bears / nathan@rtfm.net \/ and the dumber visitors intersect." / finger for PGP key \ Steve Thompson, Yosemite wildlife biologist 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?199807031202.IAA02018>