From mboxrd@z Thu Jan 1 00:00:00 1970 From: jtc@redback.com (J.T. Conklin) To: Andrew Cagney Cc: Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: parcelling up struct gdbarch Date: Mon, 16 Jul 2001 12:34:00 -0000 Message-id: <5mae24vfc1.fsf@jtc.redback.com> References: <20010713001635.A19524@nevyn.them.org> <3B4F4D7F.6010201@cygnus.com> <20010713145356.A4898@nevyn.them.org> <3B506250.5080502@cygnus.com> <20010716112536.A19620@nevyn.them.org> <3B533AAD.1060300@cygnus.com> X-SW-Source: 2001-07/msg00182.html >>>>> "Andrew" == Andrew Cagney writes: >> legacy_breakpoint_from_pc, default_memory_insert_breakpoint, etc. It >> also brings in gdb_stdout, which means we need main.o. It's hopeless. Andrew> If GDBserver is going to be come more tightly integrated into GDB then Andrew> it is going to need to pick up some baggage like ui-file. Can you explain your vision (or provide pointers to previous articles) of a tightly integrated gdbserver? I expect and accept some baggage, but at the moment I cannot comprehend why it would need high level constructs like ui-file. --jtc -- J.T. Conklin RedBack Networks