From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) by sourceware.org (Postfix) with ESMTPS id E547A3858D3C for ; Tue, 19 Apr 2022 22:47:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E547A3858D3C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wr1-f53.google.com with SMTP id k22so24330951wrd.2 for ; Tue, 19 Apr 2022 15:47:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=QlJQPX7UHZUNict21UxGa4L6n7S2wMgdHob3hq2YGSI=; b=R056WhAcMLMOxcJEskrAcncs2rjKw0JI5UVDAvDB+jtJ6JRA6tU2ps8xQH0xSaCe79 TwJgG6LjR8UxgvFmZzWc1XybY+6IzUPU/jZ/gA1ry5qCPa4WEG737SpVjGlBEX//kdVb G6itSQVwEG1RywAY26y2hu+wnZlZ0SljH3NZs3MSp9dDs+q263dmyFrXAURc3kgeU9j/ bRtYZTpSlFpaNPnmODojNoVv1kvd6di+sK5a0zwyKO0FW46swgTT8cmVx6FGU0YT4Nqn ZB64nMXU2Mf/l1pApBFFNhUEGATHnEInQckqyFPx4H0GCqFfdpMvliI6l3bhVqz+2ZIK qE6w== X-Gm-Message-State: AOAM530sqS38KS/2fYoOaUNUCqMlPcjHNHomNrHqwVrAc5BxfJrrCeLt Wzg0xTjDvMdKyyLGq6vMPoGIKGkhNUY= X-Google-Smtp-Source: ABdhPJxoFyIkd262uV5skwg3tA4hPBf2A8wMGkl3NDWUhY0Z+otltR/eUMxGU9gSIMZSZ391taWDVQ== X-Received: by 2002:a5d:584c:0:b0:20a:821a:b393 with SMTP id i12-20020a5d584c000000b0020a821ab393mr13815210wrf.141.1650408461409; Tue, 19 Apr 2022 15:47:41 -0700 (PDT) Received: from localhost ([2001:8a0:f924:2600:209d:85e2:409e:8726]) by smtp.gmail.com with ESMTPSA id r10-20020a7bc08a000000b0039049f8b3f9sm15239269wmh.27.2022.04.19.15.47.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Apr 2022 15:47:40 -0700 (PDT) From: Pedro Alves To: gdb-patches@sourceware.org Subject: [PATCH 0/2] Fix gdbserver/linux memory access regression Date: Tue, 19 Apr 2022 23:47:37 +0100 Message-Id: <20220419224739.3029868-1-pedro@palves.net> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2022 22:47:44 -0000 The recent change to make GDBserver always access memory via /proc/pid/mem caused a regression in gdb.threads/access-mem-running-thread-exit.exp that I somehow missed. This is actually a pre-existing GDBserver issue being now exposed. Patch #2 fixes the GDBserver bug. Patch #1 fixes the gdb.threads/access-mem-running-thread-exit.exp testcase itself -- it doesn't run properly against --target_board=native-extended-gdbserver today. Pedro Alves (2): Fix gdb.threads/access-mem-running-thread-exit.exp w/ native-extended-gdbserver gdbserver: track current process as well as current thread .../access-mem-running-thread-exit.exp | 30 ++++++++++++- gdbserver/gdbthread.h | 1 + gdbserver/inferiors.cc | 26 ++++++++--- gdbserver/server.cc | 4 +- gdbserver/target.cc | 44 ++++++++++++++++++- gdbserver/target.h | 15 ++++++- 6 files changed, 108 insertions(+), 12 deletions(-) base-commit: 6ea673e2d643b7b2283aa73d35b02dfc9aa7115f -- 2.26.2