Re: [patch] Fix a crash when displaying variables from shared ?library.

[Paul Pluzhnikov <ppluzhnikov@google.com>]

On Tue, Mar 17, 2009 at 8:15 PM, Joel Brobecker <brobecker@adacore.com> wrote:

> If I understand the original issue correctly, we need to restart
> the execution of our program in order to demonstrate the issue.

Well, not really. You could also
  dlopen foo.so
  break in foo.so
  display something referring to foo.so symbols
  dlclose foo.so
  re-display

But writing a portable test for that is harder.

> Except with the extended-remote protocol, we can't do that when
> using the gdbserver, right? In other words, the "run" command with
> target remote doesn't restart the program like in the native case.
> So I'd say we kill the test for remote targets.

Is it as simple as removing changing fail to untested:

if { [gdb_start_cmd] < 0 } {
-    fail "Can't run to main (2)"
+    untested "Can't run to main (2)"
    return 0
}

Of course we might just as well skip the test, since it's not going
to test much in that case.


-- 
Paul Pluzhnikov