Date: Fri, 3 Jul 1998 09:19:02 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: kuku@gilberto.physik.RWTH-Aachen.DE Cc: marc@bowtie.nl, kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-hackers@freefall.cdrom.com Subject: Re: trace/KTRACE Message-ID: <199807031419.JAA10403@detlev.UUCP> In-Reply-To: <19980703141950.02992@gil.physik.rwth-aachen.de> (message from Christoph Kukulies on Fri, 3 Jul 1998 14:19:50 %2B0200) References: <199807030924.LAA20365@gilberto.physik.RWTH-Aachen.DE> <199807031209.OAA24029@bowtie.nl> <19980703141950.02992@gil.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> I would like to find out where an application 'hangs' for >>> some overly long time (possibly a network/socket call or something) >>> 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. > I believe the mentioned 'truss' seems to do what I want. When gdb attaches to a process, it halts it. You can then do a backtrace to find what's going on. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped 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?199807031419.JAA10403>