From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30793 invoked by alias); 24 Jul 2015 18:17:17 -0000 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 Received: (qmail 30781 invoked by uid 89); 24 Jul 2015 18:17:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 24 Jul 2015 18:17:16 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id E3D45ADAFB; Fri, 24 Jul 2015 18:17:14 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t6OIHCtO026382; Fri, 24 Jul 2015 14:17:13 -0400 Message-ID: <55B28128.4070804@redhat.com> Date: Fri, 24 Jul 2015 18:17:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Simon Marchi , "Breazeal, Don" CC: GDB Patches Subject: Re: [PATCH 3/N] remote follow fork and spurious child stops in non-stop mode References: <1437672294-29351-1-git-send-email-palves@redhat.com> <55B1308E.4020700@redhat.com> <55B27E71.1090705@ericsson.com> In-Reply-To: <55B27E71.1090705@ericsson.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-07/txt/msg00709.txt.bz2 On 07/24/2015 07:05 PM, Simon Marchi wrote: > I tried it and it works as expected. If you try the same test program in all-stop > though, fork childs are left stopped. Is it expected? I am not sure how forking > interacts with all-stop. Yeah, in all-stop, you need "set schedule-multiple on" to let all processes run. That seems to trip on more breakage: ... [Thread 0x7ffff57bc700 (LWP 11703) exited] [Thread 0x7ffff7fc1700 (LWP 11700) exited] [New Thread 0x7ffff77c0700 (LWP 11710)] [New Thread 0x7ffff67be700 (LWP 11709)] [New Thread 0x7ffff57bc700 (LWP 11711)] [New Thread 0x7ffff4fbb700 (LWP 11712)] [New Thread 0x7ffff3fb9700 (LWP 11713)] [New process 11702] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [Thread 0x7ffff3fb9700 (LWP 11713) exited] [Thread 0x7ffff4fbb700 (LWP 11712) exited] [Thread 0x7ffff57bc700 (LWP 11711) exited] [Thread 0x7ffff77c0700 (LWP 11710) exited] [Thread 0x7ffff67be700 (LWP 11709) exited] [New Thread 0x7ffff7fc1700 (LWP 11714)] [New Thread 0x7ffff6fbf700 (LWP 11716)] [New Thread 0x7ffff5fbd700 (LWP 11715)] [New Thread 0x7ffff37b8700 (LWP 11717)] [Inferior 3 (process 11634) exited normally] Cannot find new threads: generic error (gdb) info threads Cannot find new threads: generic error (gdb) info threads Cannot find new threads: generic error (gdb) q ISTR that's not a new bug, but I haven't tried older releases. Thanks, Pedro Alves