From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12287 invoked by alias); 14 Oct 2011 21:42:06 -0000 Received: (qmail 12276 invoked by uid 22791); 14 Oct 2011 21:42:05 -0000 X-SWARE-Spam-Status: No, hits=-1.8 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; Fri, 14 Oct 2011 21:41:51 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1REpVm-0002E9-9B from pedro_alves@mentor.com ; Fri, 14 Oct 2011 14:41:50 -0700 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Oct 2011 22:41:48 +0100 From: Pedro Alves To: Jan Kratochvil , Oleg Nesterov Subject: Re: FYI: fix 2 tests when glibc debuginfo is installed Date: Fri, 14 Oct 2011 21:42:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.1; x86_64; ; ) Cc: gdb-patches@sourceware.org, Tom Tromey References: <201110142219.10084.pedro@codesourcery.com> <20111014212510.GA20587@host1.jankratochvil.net> In-Reply-To: <20111014212510.GA20587@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201110142241.46746.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/msg00429.txt.bz2 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. So, 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? > The opposite - the upstream 2.6.x kernel state - was IMO worse, it was resumed > and one could not safely keep it stopped. > > > > Why was the behavior changed incompatibly if we're having the all new > > PTRACE_SEIZE? Do you have a lkml reference to the change? > > I do not have anything specific, AFAIK it just happened as part of all the > changes incl. PTRACE_SEIZE. I have updated the behavior into two new *-3x.c > tests with Oleg Nesterov ~review/check/approval in: > http://sourceware.org/systemtap/wiki/utrace/tests -- Pedro Alves