* MI and remote debugging
@ 2002-02-09 20:03 Daniel Jacobowitz
2002-02-12 22:26 ` Andrew Cagney
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Jacobowitz @ 2002-02-09 20:03 UTC (permalink / raw)
To: gdb
Any remote config (like gdbserver, or even monitor, I think...) that
overrides gdb_target_cmd/gdb_file_cmd loses because of the static mi version
in mi-support.exp. This leads to almost a day's worth of timeouts. I've
tried to cobble together a gdbserver version of mi_gdb_file_cmd and an
mi-aware mi_gdb_target_cmd; I can't do it.
Andrew, any thoughts?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MI and remote debugging
2002-02-09 20:03 MI and remote debugging Daniel Jacobowitz
@ 2002-02-12 22:26 ` Andrew Cagney
2002-02-12 22:41 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Cagney @ 2002-02-12 22:26 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: gdb
> Any remote config (like gdbserver, or even monitor, I think...) that
> overrides gdb_target_cmd/gdb_file_cmd loses because of the static mi version
> in mi-support.exp. This leads to almost a day's worth of timeouts. I've
> tried to cobble together a gdbserver version of mi_gdb_file_cmd and an
> mi-aware mi_gdb_target_cmd; I can't do it.
>
> Andrew, any thoughts?
For targets other than ``target remote'' I don't think we need to be too
concerned. However, ``target remote'' variants should work. I know it
works for SID (a remote simulator).
Can you expand a little.
Andrew
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MI and remote debugging
2002-02-12 22:26 ` Andrew Cagney
@ 2002-02-12 22:41 ` Daniel Jacobowitz
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2002-02-12 22:41 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
On Wed, Feb 13, 2002 at 01:26:04AM -0500, Andrew Cagney wrote:
> >Any remote config (like gdbserver, or even monitor, I think...) that
> >overrides gdb_target_cmd/gdb_file_cmd loses because of the static mi
> >version
> >in mi-support.exp. This leads to almost a day's worth of timeouts. I've
> >tried to cobble together a gdbserver version of mi_gdb_file_cmd and an
> >mi-aware mi_gdb_target_cmd; I can't do it.
> >
> >Andrew, any thoughts?
>
> For targets other than ``target remote'' I don't think we need to be too
> concerned. However, ``target remote'' variants should work. I know it
> works for SID (a remote simulator).
>
> Can you expand a little.
For target remote it does not necessarily work. Look at
config/gdbserver.exp to see what you need to do to spawn a gdbserver on
load; mi overrides that function entirely. The comment
"# ``gdb_file_cmd''" in mi_gdb_file_cmd appears to be as close as we
come to thinking about this.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-02-13 6:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-09 20:03 MI and remote debugging Daniel Jacobowitz
2002-02-12 22:26 ` Andrew Cagney
2002-02-12 22:41 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox