[v2,1/6,gdb/testsuite] Add gdb.testsuite/lock.exp
Checks
| Context |
Check |
Description |
| linaro-tcwg-bot/tcwg_gdb_build--master-aarch64 |
success
|
Build passed
|
| linaro-tcwg-bot/tcwg_gdb_build--master-arm |
success
|
Build passed
|
Commit Message
I noticed there's no test-case for lock_file_{acquire,release}.
Add gdb.testsuite/lock.exp.
---
gdb/testsuite/gdb.testsuite/lock.exp | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 gdb/testsuite/gdb.testsuite/lock.exp
base-commit: 4ba6bd8393418b63dc3efa0ec6f934903a10f140
new file mode 100644
@@ -0,0 +1,28 @@
+# Copyright 2026 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+set lockfile [build_standard_output_file "lock.txt"]
+gdb_assert {![file exists $lockfile]} "Initial"
+
+# Scenario 1:
+# - acquire 1
+# - release 1
+with_test_prefix "simple" {
+ set res [lock_file_acquire $lockfile]
+ gdb_assert {[file exists $lockfile]} "Acquire lock"
+
+ lock_file_release $res
+ gdb_assert {![file exists $lockfile]} "Release lock"
+}