This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: catch load/unload not implemented on any target (remove?)
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 27 Oct 2008 06:14:33 +0200
- Subject: Re: catch load/unload not implemented on any target (remove?)
- References: <20081027004044.GA3907@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sun, 26 Oct 2008 17:40:44 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> I am conflicted as to what to do in the meantime: Leave the code as is,
> and update the documentation that this feature is currently implemented
> on no platform. Or remove the code entirely.
>
> I am leaning towards removing the code entirely, for several reasons:
> - Documentating a feature as unimplemented seems silly;
> - I don't think there is much in the current code that once can
> reuse in order to implement this feature properly
> - When someone is ready to implement this feature again for his platform,
> there shouldn't be much to do in terms of infrastructure work to do at
> the breakpoint module level. So it shouldn't be very difficult to
> implement. There might be one little difficulty based on the fact
> that some architectures will implement this feature using a phyical
> breakpoint (eg: svr4) whereas others won't (eg: Windows), but that
> shouldn't be very difficult to handle by using the right bp_kind.
>
> Thoughts?
Given what you describe, I'm okay with removing that code.