From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B54443886C44; Thu, 27 Oct 2022 07:19:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B54443886C44 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1666855182; bh=4vEEPp5P+TwcaBNNMeBX/0CdELT/TCVRnEbrann6Ras=; h=From:To:Subject:Date:From; b=w1qwjIg/AP5c/6QxFk+BtaM8WuvLONhdRS3+5P3egIpNAJitP2qi0B9SUsCxCLQlL oScDqissWGb2jZoxzWS5UMASM5QWBc3hd7Nku362QOejct4KM4LcoauP/loK8hR+Iz HM753PaHUWe5QvudI9zup0mYtNdqUbE/6luOnBPs= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/29726] New: [gdb] FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=delete: connection to GDBserver succeeded Date: Thu, 27 Oct 2022 07:19:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29726 Bug ID: 29726 Summary: [gdb] FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=3D: action=3Ddelete: connection to GDBserver succeeded Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I build gdb using -O2, and ran the testsuite using taskset -c 0, and ran in= to: ... (gdb) PASS: gdb.server/connect-with-no-symbol-file.exp: sysroot=3D: action=3Ddelete: setup: adjust sysroot builtin_spawn /home/vries/gdb_versions/devel/build/gdb/testsuite/../../gdb/../gdbserver/g= dbserver --once localhost:2385 /home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/conne= ct-with-no-symbol-file/connect-with-no-symbol-file^M /bin/bash: /home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/conne= ct-with-no-symbol-file/connect-with-no-symbol-file: Permission denied^M /bin/bash: line 0: exec: /home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/conne= ct-with-no-symbol-file/connect-with-no-symbol-file: cannot execute: Permission denied^M During startup program exited with code 126.^M Exiting^M target remote localhost:2385^M `/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/conn= ect-with-no-symbol-file/connect-with-no-symbol-file' has disappeared; keeping its symbols.^M localhost:2385: Connection timed out.^M (gdb) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=3D: action=3Ddelete: connection to GDBserver succeeded ... AFAICT, the following is intended to happen: - enter scenario "permission" - cp $exec.bak $exec - disconnect - gdbserver start with $exec - chmod 000 $exec - connect to gdbserver - detach - enter scenario "delete" - cp $exec.bak $exec - disconnect - gdbserver start with $exec - delete $exec - connect to gdbserver - detach So, it looks like the second "gdbserver start with $exec" fails because it = has no permission to execute $exec, which at first glance suggest that the chmod 000 $exec is still effective, despite the subsequent "cp $exec.bak $exec" w= hich should have restored the permissions. FTR, the $exec.bak still has the correct permissions set: ... $ ls -al outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file.= bak -rwxr-xr-x 1 vries users 12104 Oct 26 18:00 outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file.= bak ... And due to the "delete $exec", we can't see the permissions of that one. This doesn't look like a gdb bug, but I have no idea yet what it could be. --=20 You are receiving this mail because: You are on the CC list for the bug.=