From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id VwIUN8c5LGPkMz4AWB0awg (envelope-from ) for ; Thu, 22 Sep 2022 06:32:39 -0400 Received: by simark.ca (Postfix, from userid 112) id D67D01E112; Thu, 22 Sep 2022 06:32:39 -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=B5mOu8MB; 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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.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 3EE4C1E0D3 for ; Thu, 22 Sep 2022 06:32:39 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C7AE638582AE for ; Thu, 22 Sep 2022 10:32:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C7AE638582AE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1663842757; bh=qK7ure31hbbmglY45fussEIPJU4+MTAZgcDWGxggd3c=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=B5mOu8MB6/6gtuaVRvxxsa/CCSATdNXCAC6Yb9IZpo5E03in2Gj9QNUFqMgSF3nw6 d6oikW40eLt3Ayi9epVkJayJWIB3iGI3/L1l4yVt1Cy5QsOPMLJ3OLnbfdZtJZ0NRU eRqOPzQdth7IDeZyu0BZlp5xTBFYOdIXBf9bM8Bs= Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) by sourceware.org (Postfix) with ESMTPS id 0757C3858438 for ; Thu, 22 Sep 2022 10:31:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0757C3858438 Received: by mail-lf1-x136.google.com with SMTP id x27so14017161lfu.0 for ; Thu, 22 Sep 2022 03:31:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=qK7ure31hbbmglY45fussEIPJU4+MTAZgcDWGxggd3c=; b=WACeF3cAAU5QdszK09Zx8bmWfswxljj11BuE9rtWGtlQKK59cW0FFWjjQ/wkeiE2KH fY7ZauiVUBS7w2W5cTqjxWpNYM31VMbjbyQd++Bux4IlYpLm1MxpmBpaWyNsfTIEDi1d Rfnsu9VGFRO0k/iqQOyr0B9Nc7kniZpMerMlL2okermatwN8aqBuZC/iVYOoJW8T+1e/ 0cuIXJjiNAc3rb1fqWzDonDewb502vQOOAiC4PUC4IdvAjEoMAA2myIAVimy9xFVVeH+ km5UeaX/57BAxpM+sShky4ub+FpUWCD8C19hoi5ioOP9D6U+HVun2zP+mbr1xbGiZtNg aC8A== X-Gm-Message-State: ACrzQf0fW3d7t5EHXFQZnpTxfPTKAIMaDPaTAjiljsFQt+ly1j5wGRk/ /1xpwRPDMhaNXqGHsALRysPg09qCObFMGKZow0lD/gQD0fFJfA== X-Google-Smtp-Source: AMsMyM7TJoVj/gM3Yxz5M/2I2Vj166PLMbJb1FKo6tzF1AthTnkMMVBh7V6GTOxlFEIO23VwD2MFNYtl8gybzyjtPIk= X-Received: by 2002:a05:6512:3da1:b0:49f:1b3d:88b9 with SMTP id k33-20020a0565123da100b0049f1b3d88b9mr909794lfv.67.1663842693003; Thu, 22 Sep 2022 03:31:33 -0700 (PDT) MIME-Version: 1.0 Date: Thu, 22 Sep 2022 13:31:21 +0300 Message-ID: Subject: Running testsuite on QEMU (sorry if possible duplicate) To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" 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: Konstantin Vladimirov via Gdb Reply-To: Konstantin Vladimirov Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hi, My colleague Ivan already sent this question to this mailing list, but it looks like his email hasn't landed. We are trying to run dejagnu/gdb testsuite on QEMU (RISCV) on Linux. Some tests that pass on the local machine fail as they expect having shared libs or other binary files at hardcoded paths on a machine (QEMU in our case) where the binary is running. Question is: is it ok to patch gdb testsuite to get rid of hardcoded paths. Or maybe this is something intentional? Example: gdb.base/print-file-var.exp, see SHLIB_NAME variable. --- With best regards, Konstantin