From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id OXumFt2OS2RffzgAWB0awg (envelope-from ) for ; Fri, 28 Apr 2023 05:16:13 -0400 Received: by simark.ca (Postfix, from userid 112) id 4FDE61E221; Fri, 28 Apr 2023 05:16:13 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=UPIAG0O3; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 31BF11E128 for ; Fri, 28 Apr 2023 05:16:11 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 637FC3857019 for ; Fri, 28 Apr 2023 09:16:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 637FC3857019 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1682673370; bh=1uX9KHucgRr3wqAhs8rbi0sN6D+AAC018ZlntZ7LxOM=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=UPIAG0O3qsmOvM8JUEwaZjmgYnAgD4fn8r+yB8F8fnePgql652AfW+iYKqfoW+tCL X/B2leS8mbguJRBUHPQb5iEfs3/RBtgtm5PGNdvCCPD+JeCsijDflcGbZi02zdkKND tKR0kUp7czwK1njbaq8Z2AhJol2IsF54Z0P0hiPg= Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) by sourceware.org (Postfix) with ESMTPS id 055533858C31 for ; Fri, 28 Apr 2023 09:14:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 055533858C31 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-50506111a6eso17601043a12.1 for ; Fri, 28 Apr 2023 02:14:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682673270; x=1685265270; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=o6qDrS2v6Tj4xHAJ4QRaGlwumR6aUf7u+m2GF1yPe1c=; b=MWUbnh9zdbXP8iITboeJ95v5SSVNw23UcQSKKXeYYfSU54hH1/Q+Pr2GOPEb5NaF5+ gfSg8M9SFCVLxy1175tUG+tuIc7WqpqDHzAa9xoxeuRHzjvMwxcbyIxksfx/2p1/zoKB Oc1l2gtielSq3XXHsj97nZtfHq4ntmIeXcvKcEzqQ5fA3tP4DAQu0KN+FI/KUZpALHkW 4Hbe216aXvW2BWUz3cbnTIrpZVHD0bxHkUlXIavH6UY9kD0zrnltzCTHurn26OfIbC+V wR54OV7/r3/GZh/mAJg0WWV56KCa+6IAQlYZUmp+HwfN/l3i+tuyNWntRlAWYSOgtgRp UZNg== X-Gm-Message-State: AC+VfDzJzL2OLmkziL7C6WrSCf/x0zugANH6ZZWss3xwgK6NC982sVN+ yXwYVILkJ6xjNv39UgE4K4sxUXTDlw7vOYjp1eGtZhPgQhQ= X-Google-Smtp-Source: ACHHUZ5ZKM7i3AJmOFz5Zux5gx6LQtmqnHCDl4pXV5zi4TB6VvaIL7WIwCbEfeT1YiUJ4ivOsMPlfCSRNErAH2iOvdM= X-Received: by 2002:aa7:cccb:0:b0:50a:2e0:eef8 with SMTP id y11-20020aa7cccb000000b0050a02e0eef8mr4044746edt.21.1682673269636; Fri, 28 Apr 2023 02:14:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 28 Apr 2023 21:14:22 +1200 Message-ID: Subject: Re: Problems interrupting remote target on powerpc To: GDB Mailing list Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Chris Packham via Gdb Reply-To: Chris Packham Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" On Thu, 27 Apr 2023, 4:55 PM Chris Packham, wrote: > Hi GDB, > > I've had a few users report to me issues with interrupting a running > process after continuing when attached to a remote gdbserver running > on a powerpc target. Everything seems to work properly on arm and > aarch64 so there might be some powerpc or big-endian specific issue > lurking. > > The gdbserver version we're currently using is from gdb-11.2 built > from source and most users have gdb-multiarch 12.1 from ubuntu 22.04 > (some might still be using gdb-multiarch 10.2 from a PPA). > > Does this ring any bells for anyone? I'm going to try and get hold of > a powerpc target to test with to see if I can reproduce it for myself. > > Thanks, > Chris > Did some digging of my own I can report that indeed things aren't working well for powerpc. I tried updating gdbserver to 12.1 and 13.1. 12.1 was much the same as 11.2. 13.1 reported that it was unable to send sigkill when processing the interrupt command. 13.1 also seems not to be able to respond to the 'info os processes' command from the gdb client >