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: RFA: Support Windows extended error numbers in safe_strerror


> Date: Sat, 4 Feb 2006 23:39:17 -0800
> From: Jim Blandy <jimb@red-bean.com>
> Cc: gdb-patches@sourceware.org
> 
> On 2/4/06, Eli Zaretskii <eliz@gnu.org> wrote:
> > > Date: Sat, 4 Feb 2006 21:01:14 -0500
> > > From: Daniel Jacobowitz <drow@false.org>
> > >
> > > I think that mingw32 hosting support and mingw32 native support can be
> > > treated separately; do you disagree?
> >
> > I do.  I think they should be treated together, as having a cross
> > debugger that cannot debug natively is kinda silly.
> 
> I don't think it's silly.  If you are using Windows as a platform for
> cross-development, you may not even have shelled out the bucks for a
> native compiler.  In that situation, why would it be ridiculous to
> have a debugger that, like your compiler, is only useful debugging
> programs on your cross target?

Reality check: how many other non-embedded platforms have their cross-
and native targets separated?

> Also, the kinds of things needed to host GDB on a platform are best
> kept partitioned away from the stuff needed for doing native target
> debugging, simply as a matter of design.  It's a simple matter of
> separation of concerns.

Then please explain why do we compile ser-unix.c with native Unix
targets, and ser-go32.c with the DJGPP native target.


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