From owner-freebsd-current@FreeBSD.ORG Wed Sep 21 07:44:02 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B5FA106564A for ; Wed, 21 Sep 2011 07:44:02 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id B907A8FC12 for ; Wed, 21 Sep 2011 07:44:01 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R6HTM-0006mw-5I for freebsd-current@freebsd.org; Wed, 21 Sep 2011 09:44:00 +0200 Received: from 178.214.36.169 ([178.214.36.169]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Sep 2011 09:44:00 +0200 Received: from citrin by 178.214.36.169 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Sep 2011 09:44:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Anton Yuzhaninov Date: Wed, 21 Sep 2011 07:43:44 +0000 (UTC) Organization: Vega Lines: 17 Sender: Anton Yuzhaninov Message-ID: References: <4E5E46A4.3060705@citrin.ru> <4E6A99A9.1000204@delphij.net> <864o0adkva.fsf@kopusha.home.net> <86mxe0r8o5.fsf@in138.ua3> <20110919212722.GQ1511@deviant.kiev.zoral.com.ua> X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 178.214.36.169 X-Comment-To: Kostik Belousov User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/9.0-BETA2 (i386)) Subject: Re: truss X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2011 07:44:02 -0000 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 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