/* Try validating via build-id, if available. This is the most
reliable check. */
+
+ /* In case current_exec_file was changed, reopen_exec_file ensures
+ an up to date build_id (will do nothing if the file timestamp
+ did not change). If exec file changed, reopen_exec_file has
+ allocated another file name, so get_exec_file again. */
+ reopen_exec_file ();
+ current_exec_file = get_exec_file (0);
+
const bfd_build_id *exec_file_build_id = build_id_bfd_get (exec_bfd);
if (exec_file_build_id != nullptr)
{
+2020-06-21 Philippe Waroquiers <philippe.waroquiers@skynet.be>
+
+ * gdb.base/attach.exp: Test priority of 'exec-file' changed
+ over 'exec-file-mismatch'.
+ * gdb.base/attach.c: Mark should_exit volatile.
+ * gdb.base/attach2.c: Likewise. Add a comment explaining
+ why the sleep cannot be big.
+ * gdb.base/attach3.c: New file.
+
2020-06-20 Sandra Loosemore <sandra@codesourcery.com>
* gdb.mi/mi-sym-info.exp: Adjust filename patterns to make directory
return 0
}
-standard_testfile attach.c attach2.c
+standard_testfile attach.c attach2.c attach3.c
set binfile2 ${binfile}2
+set binfile3 ${binfile}3
set escapedbinfile [string_to_regexp $binfile]
#execute_anywhere "rm -f ${binfile} ${binfile2}"
-remote_exec build "rm -f ${binfile} ${binfile2}"
+remote_exec build "rm -f ${binfile} ${binfile2} ${binfile3}"
# For debugging this test
#
#log_user 1
return -1
}
+# Build the third file, used to check attach when the exec-file has changed.
+
+if { [gdb_compile "${srcdir}/${subdir}/${srcfile3}" "${binfile3}" executable {debug}] != "" } {
+ untested "failed to compile attach exec-file changed test"
+ return -1
+}
+
if [get_compiler_info] {
return -1
}
global gdb_prompt
global binfile
global binfile2
+ global binfile3
clean_restart $binfile
# Detach the process.
gdb_test "detach" "Detaching from program: .* detached\\\]" "$test detach attach"
+ # Test that the 'exec-file' changed is checked before exec-file-mismatch.
+ set test "mismatch exec-file changed has priority"
+ gdb_test_no_output "set exec-file-mismatch ask"
+ gdb_test_multiple "attach $testpid" "$test attach1 again, initial exec-file" {
+ -re "Attaching to program.*exec-file-mismatch handling is currently \"ask\".*Load new symbol table from .*attach\".*\(y or n\)" {
+ gdb_test "y" "Reading symbols from .*attach.*" $gdb_test_name
+ }
+ }
+
+
+ gdb_test "detach" "Detaching from program: .* detached\\\]" "$test detach attach initial exec-file"
+
+ # Change the exec-file and attach to a new process using the changed file.
+ remote_exec build "mv ${binfile} ${binfile}.initial"
+ remote_exec build "mv ${binfile3} ${binfile}"
+ # Ensure GDB detects ${binfile} has changed when checking timestamp.
+ sleep 1
+ remote_exec build "touch ${binfile}"
+ set test_spawn_id3 [spawn_wait_for_attach $binfile]
+ set testpid3 [spawn_id_get_pid $test_spawn_id3]
+
+ gdb_test "attach $testpid3" "Attaching to program.*attach' has changed; re-reading symbols.*" \
+ "$test attach1 again, after changing exec-file"
+ gdb_test "detach" "Detaching from program: .* detached\\\]" "$test detach after attach changed exec-file"
+
+ # Now, test the situation when current exec-file has changed
+ # and we attach to a pid using another file.
+ # Ensure GDB detects ${binfile} has changed when checking timestamp.
+ sleep 1
+ remote_exec build "touch ${binfile}"
+
+ gdb_test_multiple "attach $testpid2" "$test attach2" {
+ -re "Attaching to program.*exec-file-mismatch handling is currently \"ask\".*Load new symbol table from .*attach2\".*\(y or n\)" {
+ gdb_test "y" "Reading symbols from .*attach2.*" $gdb_test_name
+ }
+ }
+
+ # Restore initial build situation.
+ remote_exec build "mv ${binfile} ${binfile3}"
+ remote_exec build "mv ${binfile}.initial ${binfile}"
# Don't leave a process around
kill_wait_spawned_process $test_spawn_id
kill_wait_spawned_process $test_spawn_id2
+ kill_wait_spawned_process $test_spawn_id3
}
do_attach_tests
--- /dev/null
+/* This program is intended to be started outside of gdb, and then
+ attached to by gdb. Thus, it simply spins in a loop. The loop
+ is exited when & if the variable 'should_exit' is non-zero. (It
+ is initialized to zero in this program, so the loop will never
+ exit unless/until gdb sets the variable to non-zero.)
+ */
+#include <stdio.h>
+#include <stdlib.h>
+#include <unistd.h>
+
+double bidule = 0.0;
+volatile int should_exit = 0;
+
+int main ()
+{
+ int local_i = 0;
+
+ sleep( 60 ); /* System call causes register fetch to fail */
+ /* This is a known HPUX "feature" */
+ while (! should_exit)
+ {
+ local_i++;
+ }
+ return (0);
+}