Date: Wed, 21 Sep 2011 07:43:44 +0000 (UTC) From: Anton Yuzhaninov <citrin@citrin.ru> To: freebsd-current@freebsd.org Subject: Re: truss Message-ID: <j5c4jg$1t3$1@dough.gmane.org> References: <4E5E46A4.3060705@citrin.ru> <4E6A99A9.1000204@delphij.net> <j4pgu9$m94$1@dough.gmane.org> <864o0adkva.fsf@kopusha.home.net> <j57bm4$3lk$1@dough.gmane.org> <86mxe0r8o5.fsf@in138.ua3> <j57lef$a3d$1@dough.gmane.org> <j57p4t$8u8$1@dough.gmane.org> <20110919212722.GQ1511@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Sep 2011 00:27:22 +0300, Kostik Belousov wrote: KB> Could you, please, test the change below ? For me, I still can truss(1) KB> or debug with gdb after the change applied. Does truss work for you KB> with only this change, without resetting SIGTRAP handler in truss process ? KB> KB> commit 2ae586c039a55399edc3b34cd40410e0d690a16c KB> Author: Konstantin Belousov <kostik@pooma.home> KB> Date: Tue Sep 20 00:25:07 2011 +0300 KB> KB> Do not deliver SIGTRAP on exec as the normal signal, use ptracestop() KB> on syscall exit path. Otherwise, if SIGTRAP is ignored, that tdsendsignal() KB> do not want to deliver, and debugger never get a notification of exec. I can confirm - with this patch unmodified truss works when SIGTRAP is ignored. -- Anton Yuzhaninov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?j5c4jg$1t3$1>