From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24167 invoked by alias); 25 Oct 2011 16:55:41 -0000 Received: (qmail 24153 invoked by uid 22791); 25 Oct 2011 16:55:39 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 25 Oct 2011 16:55:19 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1RIkHW-00037w-BX from pedro_alves@mentor.com ; Tue, 25 Oct 2011 09:55:18 -0700 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 25 Oct 2011 17:55:16 +0100 From: Pedro Alves To: Oleg Nesterov Subject: Re: FYI: fix 2 tests when glibc debuginfo is installed Date: Tue, 25 Oct 2011 17:03:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.1; x86_64; ; ) Cc: Jan Kratochvil , gdb-patches@sourceware.org, Tom Tromey References: <201110142241.46746.pedro@codesourcery.com> <20111015144758.GA5011@redhat.com> In-Reply-To: <20111015144758.GA5011@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201110251755.12986.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00662.txt.bz2 On Saturday 15 October 2011 15:47:58, Oleg Nesterov wrote: > On 10/14, Pedro Alves wrote: > > > > On Friday 14 October 2011 22:25:10, Jan Kratochvil wrote: > > > On Fri, 14 Oct 2011 23:19:09 +0200, Pedro Alves wrote: > > > > On Friday 14 October 2011 20:37:05, Jan Kratochvil wrote: > > > > > thanks; although these testcases are broken anyway, they should be updated for > > > > > Linux kernels 3.1.x which always keep inferior stopped if it was stopped > > > > > during PTRACE_ATTACH; probably to XFAIL older kernels. > > > > > > > > Urgh. Even if you SIGCONT the process before PTRACE_DETACH? > > > > > > Yes. But I do not think it is problem, one can SIGCONT it safely after > > > PTRACE_DETACH. Just it may be (T)-stopped for a moment but why not. > > Confused... SIGCONT should work even the task is traced. It won't > resume the tracee, but it should change its (internal) state to > mark it as not-stopped. Thanks. Okay, so I take it what really happens is that PTRACE_ATTACH no longer messes with job control, and that gdb will have to `kill -SIGCONT' the inferior itself if it wants e.g., inferior function calls to work after attaching to a stopped process (or if something else SIGSTOPs the program). Hmm, feels like we got rid of some races to introduce others. > > no debugger: > > > > $ kill -SIGSTOP PID > > *stop* > > $ kill -SIGCONT PID > > *continue* > > > > with debugger: > > > > $ kill -SIGSTOP PID > > *stop* > > $ strace/gdb -p PID > > ... > > $ kill -SIGCONT PID > > ^C/detach > > *stop* > > > > Oleg, do you have a pointer to a discussion or description of the > > change? Why doesn't at least the SIGCONT cancel the stop on detach? > > It does or I missed something. -- Pedro Alves