This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: PREPARE_TO_PROCEED; Was: More multi-arch and cleanups for m68k-linux
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, gdb-patches at sources dot redhat dot com
- Date: Mon, 26 May 2003 15:52:15 -0400
- Subject: Re: PREPARE_TO_PROCEED; Was: More multi-arch and cleanups for m68k-linux
- References: <m3vfvyq2s8.fsf@whitebox.local> <3ED26D96.9060306@redhat.com>
On Mon, May 26, 2003 at 03:40:06PM -0400, Andrew Cagney wrote:
> >The only thing that prevents m68k-linux from advancing to multi-arch
> >level 2 is the PREPARE_TO_PROCEED definition in config/nm-linux.h.
> >How can this be multi-arched given that this is a native-only thing?
>
> I _think_ the current plan is along the lines of make
> generic_prepare_proceed(?) the default, and leave HP/UX as the exception.
>
> Does the generic version work on GNU/Linux? (Hmm??? nothing appears to
> currently use it!)
What timing! This is almost to the top of my todo list to redo
again...
There were three targets using their own prepare to proceed, IIRC:
mach3, hppa OSF, and HP/UX. Two of those are gone now. I believe that
generic_prepare_to_proceed will not only work on GNU/Linux (it does),
but that it will also work on HP/UX. I need to test this hypothesis.
But what does the definition of PREPARE_TO_PROCEED in config/nm-linux.h
have to do with multi-arching m68k now?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer