From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ZIZgGkmtS2QWlDgAWB0awg (envelope-from ) for ; Fri, 28 Apr 2023 07:26:01 -0400 Received: by simark.ca (Postfix, from userid 112) id 5AAB31E221; Fri, 28 Apr 2023 07:26:01 -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=Pn5AP3oe; 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 DE78E1E0D3 for ; Fri, 28 Apr 2023 07:26:00 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id D033F385840F for ; Fri, 28 Apr 2023 11:25:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D033F385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1682681159; bh=l0Li87uPrUSw7bF5VYjaJOMHH72d+3L8IMg3OQ6dM4E=; h=References:In-Reply-To:Date:Subject:To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=Pn5AP3oe4m9QZyi0yeqVoLiJluocXvjEaAHRh2wn7Do3p8Z+dmyXc0BecI/F5LA4u 6Od0A2Ff1XvlUW6BYXICRuuhcYKzslMfRzfbR0fchF6vyYnKpOo6C6lq18Ou+jC8Ef OIyZLo3ErcVlK+chfVpUnwdVJWQcnn/Hk+IR/VCk= Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by sourceware.org (Postfix) with ESMTPS id 05B5D3858D37 for ; Fri, 28 Apr 2023 11:25:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 05B5D3858D37 Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-50506ac462bso14402091a12.3 for ; Fri, 28 Apr 2023 04:25:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682681130; x=1685273130; h=cc: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=yvEFNerF4TbXa20t9H2z9pRbjOnD+MCpflc7pJRdhDg=; b=b9RuZzgOSrpMoa26pUo3qYE3GuzSxMYA6fyXgmw/miX+uT4FBlFo7S96/e7D4hTi5k Ke8oP7li7MASIztZjFFpvBjeHjSHu0qDdQ+GxT2ULhDIBDA/dPseDq4k+xiXBj65QnTO ExzYyPLpupiSJb7VRC2EAKt/z8nJIRSeQtAdp0qhWuY9jAlpk5h5GHaC3u9Cugl8g8qI fEXFGOdyjkIgDFKDD4ItY7F9koaaNIOkWTiBoDQpdeXxboRyOoJu4ZeROaKuNUI1SNFc +e2vSgRBOTcVIa5fUEKvRChK1n+WLf1bluYWqsJga1UV+aLMXYmCRJM47sce0FJEt1nh bphw== X-Gm-Message-State: AC+VfDxzYeVnIyYwQnP5CyPFHCc+x7wlyWJitIbtgjq1HD1k4U6k26rv ZKF6m7qHzF9h1m3y+ksS/ULi60X2dJ8vUHam7FqmgN9atO8= X-Google-Smtp-Source: ACHHUZ50iNO1l5pf/PwkiXrWKQEMCmkhlbw5lnVqOxandDfYq/jS+AFryy0eHftoaJ6AjusODm9ol+2z49hLhQoVEko= X-Received: by 2002:a17:906:d54c:b0:95f:a89d:efb7 with SMTP id cr12-20020a170906d54c00b0095fa89defb7mr5716512ejc.69.1682681130488; Fri, 28 Apr 2023 04:25:30 -0700 (PDT) MIME-Version: 1.0 References: <00c24cea-f256-3149-dcc7-1bad08e8bef8@arm.com> In-Reply-To: <00c24cea-f256-3149-dcc7-1bad08e8bef8@arm.com> Date: Fri, 28 Apr 2023 23:25:17 +1200 Message-ID: Subject: Re: Problems interrupting remote target on powerpc To: Luis Machado Cc: 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 Fri, 28 Apr 2023, 9:41 PM Luis Machado, wrote: > On 4/28/23 10:38, Chris Packham wrote: > > > > > > On Fri, 28 Apr 2023, 9:19 PM Luis Machado, > wrote: > > > > On 4/28/23 10:14, Chris Packham via Gdb wrote: > > > On Thu, 27 Apr 2023, 4:55 PM Chris Packham, < > judge.packham@gmail.com > 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 > > > > > >> > > > > What sort of behavior/output do you see? > > > > > > I'll capture some proper output when I'm back in the office but > basically once I 'continue' I can't get the gdb prompt back with Ctrl+C. > > > > Is it a tight loop by any change? Or is gdb trapped in a long sequence of > instruction-steps? > It's a daemon using a g_main_loop() not sure if that counts as a tight loop. GDB shouldn't be doing any stepping. I'll also give a process that runs and finishes when I get a chance to see if there are issues with that. >