From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) by sourceware.org (Postfix) with ESMTPS id 2D582385502A for ; Fri, 11 Jun 2021 17:55:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2D582385502A 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-f54.google.com with SMTP id a20so6982567wrc.0 for ; Fri, 11 Jun 2021 10:55:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rjZYn/Kt+NpSvFdEYJ/BQaEwvDH9rAnu+IFOokTHL7o=; b=UbD5zSrMU+iAiDVjFvK/T/aAgQrEq1JyKujS3MFsxS/Xw2lSYt/YdqVJcrfOR1X+Ax vIpn47SC0cS+boo42BkDa9wMtVEcboB7VXPLTHhSvuqOsggIqzlvwNPFTxsWIC9G84f7 cUybGE7UaU2YFe2vHrAbi5H+olopvQaAYndwAwGBeIVpuRLTYW3/evEjnqR+AkAnPzPs M0MuCac/UJ5+eMS11kc1krgTIpxad6bUXxO4zYkbXugX3Q9QVO5nJtfxTR7xVpjwFVig JF5HjmeVHI/uYc/hRIGyKgfuaT3v6ZhaJF1R/K4P605acvLF2gEPJnKFFZj7FgHLlZA3 zjsg== X-Gm-Message-State: AOAM532yBOFivyPAIT6lGXZ2ruAzg+7H4uQfw8AwbJJLLCLpcXH0KkMP Yax4ugrSqJdgU1bqGykA2AEGQdRJhmoIqg== X-Google-Smtp-Source: ABdhPJxauNuATRnWMPCdkLo5p4sHzzbiyIJo2OyvQzww8nyMIJssBx2sH2dXW+T1yxoNK1hvdjyw/w== X-Received: by 2002:a5d:67d2:: with SMTP id n18mr5373645wrw.158.1623434109589; Fri, 11 Jun 2021 10:55:09 -0700 (PDT) Received: from ?IPv6:2001:8a0:f932:6a00:6b6e:c7b6:c5a7:aac3? ([2001:8a0:f932:6a00:6b6e:c7b6:c5a7:aac3]) by smtp.gmail.com with ESMTPSA id b8sm14065104wmd.35.2021.06.11.10.55.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Jun 2021 10:55:08 -0700 (PDT) Subject: Re: [PATCH] Linux: Access memory even if threads are running From: Pedro Alves To: gdb-patches@sourceware.org References: <20210611173616.3854098-1-pedro@palves.net> Message-ID: <715301cd-0e73-fa91-baec-9123cae0fc2f@palves.net> Date: Fri, 11 Jun 2021 18:55:07 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210611173616.3854098-1-pedro@palves.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Fri, 11 Jun 2021 17:55:13 -0000 On 2021-06-11 6:36 p.m., Pedro Alves wrote: > #1 - gdb.threads/access-mem-running.exp > > This is the conceptually simplest - it has two threads, and has GDB > read and write memory from each of the threads. It also tests > setting a breakpoint while all threads are running, and checks that > the breakpoint is hit immediately. Hmm, after pressing send, I realized that this testcase doesn't have to be multithreaded -- if I make it single-threaded, then it becomes runnable against more targets. The multi-threading aspect it was testing is already covered by the other testcase. I've send a v2 with that change shortly... Thanks, Pedro Alves