Date: Fri, 03 Jul 1998 14:31:34 +0200 From: Marc van Kempen <marc@bowtie.nl> To: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> Cc: marc@bowtie.nl, freebsd-hackers@freefall.cdrom.com Subject: Re: trace/KTRACE Message-ID: <199807031231.OAA25687@bowtie.nl> In-Reply-To: kuku's message of Fri, 03 Jul 1998 14:19:50 %2B0200. <19980703141950.02992@gil.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, Jul 03, 1998 at 02:09:52PM +0200, Marc van Kempen wrote: > > > 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? > > > > > Can't you use gdb and attach to the running process? > > > > gdb 'progname' 'pid' > > And then? How would I see what the program is doing? ^C-ing is > not what I wish. > If you attach to it, while it seems to hang, it will display the function it is currently executing. You don't have to abort the program. It is just a normal debugging session. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- 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?199807031231.OAA25687>