This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


> The problem is that gdb_start_cmd is a nop for remote targets:
[...]
> What do you think?  Should we skip this test for remote
> targets, or perhaps we do things differently here?

If I understand the original issue correctly, we need to restart
the execution of our program in order to demonstrate the issue.
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.

-- 
Joel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]