From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id CC72E3858D35 for ; Thu, 22 Jun 2023 13:17:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CC72E3858D35 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1687439857; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RG5023KdDtIMbzhsW7myw6S3CHkpbT3b5KaIIVCfpM0=; b=ZSi4uQbnhNYk53eZWk5oZobKkjhwEIDLt4SfInEy/C1Cqj4m2Fgz01rWSp4ONn686BFYU2 exqnFlxb3mNEjZcFBEIoideiophCJ5HBn1Zp6MwQE/XrnHtWV+CAnSM4cY63BfdYjq0gZM d1UnP3jDvgP0sGg6PAKI6bUqDfCK+Zg= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-392-clsbUH4LPXuuOHdb4ljpag-1; Thu, 22 Jun 2023 09:17:36 -0400 X-MC-Unique: clsbUH4LPXuuOHdb4ljpag-1 Received: by mail-lf1-f69.google.com with SMTP id 2adb3069b0e04-4f957270b92so1959283e87.1 for ; Thu, 22 Jun 2023 06:17:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687439853; x=1690031853; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RG5023KdDtIMbzhsW7myw6S3CHkpbT3b5KaIIVCfpM0=; b=FojwwSCYuRKB5fBKJxEf+jYT/Zp3UzNIdGAtYYLEgF+vTFmBASDVtHQFqg8enQp6xR CNz/HJY7JI61r8UliIcUZoIaMV2XIKywHrzLuYeSElNY15e2zqmDDY8/f5J5Dntj88y/ cUiKsycoILrXiUeSvgEWYynZRmo8jBVHbE4zfgMmBWJcT+XAr7aWoWD0Bb5s8fIP4C4X 0+0+YGTGMZ+/Jc7d8ee5+wL20P6waU4/C9ieXz429nDaanvoe6RImhQRVXEsoaOjSz8q 9enegfpHF9Z5r8o1TSNII9MQczYxrP0kKoKzQgegJ1Q1vlhFS4y4HFaHMcwa+AaRpi9k dBnA== X-Gm-Message-State: AC+VfDzgjOHdClQb9TAAw4N9j7MlvCY1vy2FkpMPki3S99GyUW4AiPl8 GfggM9xsHkGNjmBJgSTCzn+wVto1ob3UDlDtX4eOO6uA+Pxh1ba/F5AjiVQz8Y7p76w1ENJ608u PPfnsg+L92JSU/j4kCvHLxWoZWSejz5loGUQ+GxcUtBeIyqvRzdScJZc4VAGR/xloTtu85VWs8P ycAxHx3A== X-Received: by 2002:ac2:5059:0:b0:4f8:65ef:afc2 with SMTP id a25-20020ac25059000000b004f865efafc2mr8567660lfm.30.1687439853469; Thu, 22 Jun 2023 06:17:33 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5giMG6qJAMi4WhBdyHcDQUdaMxNpb+KHwZi/oQVZgHhD0Uzz9FR0P6fHMP+I/mTOVO+6h6Pw== X-Received: by 2002:ac2:5059:0:b0:4f8:65ef:afc2 with SMTP id a25-20020ac25059000000b004f865efafc2mr8567637lfm.30.1687439853033; Thu, 22 Jun 2023 06:17:33 -0700 (PDT) Received: from localhost (2.72.115.87.dyn.plus.net. [87.115.72.2]) by smtp.gmail.com with ESMTPSA id j15-20020a05600c2b8f00b003f4266965fbsm18760187wmc.5.2023.06.22.06.17.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 22 Jun 2023 06:17:32 -0700 (PDT) From: Andrew Burgess To: gdb-patches@sourceware.org Cc: Andrew Burgess Subject: [PATCH 0/8] Some vfork related fixes Date: Thu, 22 Jun 2023 14:17:20 +0100 Message-Id: X-Mailer: git-send-email 2.25.4 MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: While reviewing this patch: https://inbox.sourceware.org/gdb-patches/20230612074927.424961-2-christina.schimpe@intel.com/ I spotted a block of code which I wasn't certain the meaning of. So I started looking into the history of the code, and started testing it a little, and ran into 3 vfork related bugs, which this series fixes. Patches #1, #6, and #7 are all about updating an existing test to test vfork a little more, Patches #2, #3, and #5 are the three fixes, Patch #4 is the original refactoring patch referenced above, And patch #8 adds some extra debug output. --- Andrew Burgess (7): gdb: catch more errors in gdb.base/foll-vfork.exp gdb: don't restart vfork parent while waiting for child to finish gdb: fix an issue with vfork in non-stop mode gdb: don't resume vfork parent while child is still running gdb/testsuite: expand gdb.base/foll-vfork.exp gdb/testsuite: remove use of sleep from gdb.base/foll-vfork.exp gdb: additional debug output in infrun.c and linux-nat.c Mihails Strasuns (1): gdb, infrun: refactor part of `proceed` into separate function gdb/infrun.c | 180 +++++--- gdb/linux-nat.c | 32 +- gdb/testsuite/gdb.base/foll-vfork.exp | 588 ++++++++++++-------------- 3 files changed, 403 insertions(+), 397 deletions(-) base-commit: 07a88d7f2121630956997bc5edd495af40d4494f -- 2.25.4