[patch] Re: "optimized out" on gdb.base/gdb1090.exp

[Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>]

Thanks Jan for reviewing this. This is the updated patch with the suggested modifications.

Checking out the original PR 1090 that originated this testcase, it doesn't mention any particularity regarding frame or backtrace, which leads me to believe that changing where 'print' is called should not affect the main focus of the testcase.

Thanks,
-- 
Edjunior

2011-04-12  Edjunior Machado  <emachado@br.ibm.com>

	* testsuite/gdb.base/gdb1090.exp: change breakpoint location to	read the
	content of 's24' correctly (avoiding "optimized out").
	* testsuite/gdb.base/gdb1090.c: add comment in order to set breakpoint.

diff --git a/gdb/testsuite/gdb.base/gdb1090.c b/gdb/testsuite/gdb.base/gdb1090.c
index 22f2cec..8933952 100644
--- a/gdb/testsuite/gdb.base/gdb1090.c
+++ b/gdb/testsuite/gdb.base/gdb1090.c
@@ -36,7 +36,7 @@ void foo ()
    register struct s_2_by_4 s24;
    s24.field_0 = 1170;
    s24.field_1 = 64701;
-  marker (s24);
+  marker (s24); /* break-here */
    return;
  }
  
diff --git a/gdb/testsuite/gdb.base/gdb1090.exp b/gdb/testsuite/gdb.base/gdb1090.exp
index a15fd04..ab568ab 100644
--- a/gdb/testsuite/gdb.base/gdb1090.exp
+++ b/gdb/testsuite/gdb.base/gdb1090.exp
@@ -40,11 +40,13 @@ gdb_start
  gdb_reinitialize_dir $srcdir/$subdir
  gdb_load ${binfile}
  
-if ![runto marker] then {
-    perror "couldn't run to breakpoint"
-    continue
-}
-gdb_test "up" ".*foo.*" "up from marker"
+if ![runto_main] then {
+    fail "Can't run to main"
+    return 1
+}
+
+gdb_breakpoint [gdb_get_line_number "break-here"]
+gdb_continue_to_breakpoint "break-here" ".* break-here .*"
  
  gdb_test_multiple "print s24" "print s24" {
      -re "\\\$\[0-9\]* = \\{field_0 = 1170, field_1 = 64701\\}\r\n$gdb_prompt $" {