From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6261 invoked by alias); 8 Jun 2005 18:33:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6243 invoked by uid 22791); 8 Jun 2005 18:33:10 -0000 Received: from qnxmail.qnx.com (HELO nimbus.ott.qnx.com) (209.226.137.76) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 08 Jun 2005 18:33:10 +0000 Received: from [10.42.102.103] (STIMPY [10.42.102.103]) by nimbus.ott.qnx.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id MPKB8FRL; Wed, 8 Jun 2005 14:33:06 -0400 Message-ID: <42A73A48.1080002@qnx.com> Date: Wed, 08 Jun 2005 18:33:00 -0000 From: Kris Warkentin User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: GDB Subject: Linux ptrace handling of SIGSTOP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg00070.txt.bz2 The Linux documentation for ptrace(PTRACE_CONT, ...., signal) claims that signal will be passed unless it is a SIGSTOP. I hit a process that I was debugging with a SIGSTOP, gdb of course stops claiming that the process got a SIGSTOP. I continue and gdb again says that the process was hit with a SIGSTOP. If I continue a second time, the process actually continues. I was debugging child_resume and observed that both times the ptrace was being called with SIGSTOP but the second time the process actually resumes. This implies to me that the ptrace documentation is not completely correct because it seems that the first SIGSTOP is being delivered. Am I missing something? The reason that I ask is that we're not currently handling SIGSTOP properly in QNX so I'm trying to find out what the expected behaviour should be. Based on the docs, I would have thought that the continue would just cause it to resume without further interruption. cheers, Kris -- Stay up-to-date on all the QNX news! Register at http://www.qnx.com/news/forms/newsletter.html to receive our newsletter.