Date: Wed, 17 Mar 2010 10:12:56 -0400 From: Alejandro Imass <ait@p2ee.org> To: FreeBSD-questions@freebsd.org Subject: Re: Kernel dump crash Message-ID: <a14066a01003170712v64347039m8f014666d80d38f8@mail.gmail.com> In-Reply-To: <a14066a01003170704y19097705ya6ec05cce4815824@mail.gmail.com> References: <c0e6d201003160513p50f6f277k88bb6e3241ca5706@mail.gmail.com> <c0e6d201003170103ra227db1m116bb8eb14a65b67@mail.gmail.com> <a14066a01003170704y19097705ya6ec05cce4815824@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 17, 2010 at 10:04 AM, Alejandro Imass <ait@p2ee.org> wrote: > On Wed, Mar 17, 2010 at 4:03 AM, Glenn Camilleri <glenncam@gmail.com> wro= te: >> Hi, >> >> >> >> I have some processes and programs that are custom made to run on FreeBS= D. I >> suspect some poor implementation of tcp in these programs, but don=92t h= ave >> the real proof. > [...] >> >> Can you kindly advise ? >> > > Using the core dump is wise but ktrace will probably be easier. Just > run like this ktrace [program] 2>&1 | less > You should be able to spot the precise failing system call quite easily > Ooops, my Linux background betrayed me, sorry (was thinking of strace). ktrace will produce a file which you later need to analyze with kdump. Running is the same but forget the output redirection, there is a -f switch to specify the outfile. > Best, > Alejandro Imass > >> >> >> BR, >> >> Glenn Camilleri >> >> -- >> Best Regards, >> Glenn Camilleri >> >> >> >> -- >> Best Regards, >> Glenn Camilleri >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a14066a01003170712v64347039m8f014666d80d38f8>