From owner-freebsd-hackers Sat Feb 9 14:58: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8766837B405 for ; Sat, 9 Feb 2002 14:58:03 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 57FFD5341; Sat, 9 Feb 2002 23:57:59 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem References: From: Dag-Erling Smorgrav Date: 09 Feb 2002 23:57:59 +0100 In-Reply-To: Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Zhihui Zhang writes: > - PT_CONTINUE + waitpid() works fine, the trace program prints out values. This is expected behaviour. > - PT_CONTINUE alone does not work but no core-dump caused by SIGTRAP > - PT_DETACH + waitpid() does not work and core-dump > - PT_DETACH alone does not work and core-dump. These three cases are unexpected. I'll have to dig some more into this, but I'm afraid I won't have time until some time next week. > Who is sending the SIGRAP (5) signal? execve(2) in kern_exec.c posts SIGTRAP if the process has debugging turned on (which it does as a result of PT_TRACE_ME). DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message