Re: [doc] Avoid conflicts between gdb and cross-gdb.

[Mike Frysinger <vapier@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

On Fri 08 Aug 2014 09:05:10 Eli Zaretskii wrote:
> > From: Mike Frysinger <vapier@gentoo.org>
> > Cc: brobecker@adacore.com, gdb-patches@sourceware.org,
> > monaka@monami-software.com Date: Thu, 07 Aug 2014 22:52:57 -0400
> > 
> > so the first question is, is this scenario important to us ?  or do we
> > consider people dealing with cross-gdb's to be on their own and to figure
> > out documentation skew problems themselves ?
> 
> I see no documentation skews here.  The GDB manual documents (barring
> errors that should be reported and fixed) describes all of its
> versions, including cross-gdb.

i described the skews in my other e-mail which you responded to.  your `info 
gdb` obviously only describes that specific version of gdb.  the further away 
your cross version gets (newer or older), the more the manual does not help 
but even confuses.  you can't even use the online gdb manual because that only 
reflects the very latest versions (unlike say gcc which archives the manual 
for every release online).  that leaves people with `man $target-gdb` which 
only describes the command line interface.

> > lumping it into the category of "if you're
> > cross-compiling/debugging, you know what you're doing" doesn't fly
> > as there a _lot_ of people who do cross work and know very little
> > here -- someone else is responsible for building/packaging the
> > toolchain and they were just given it and told "use xxx-gcc and
> > xxx-gdb".
> 
> I don't see how people who know very little could ever be able to work
> with GDB, or even with a cross-compiler, for that matter.  But I guess
> we will have to agree to disagree here.

then you obviously haven't dealt with real world customers ;).  it isn't that 
they can't look up and find information (eventually).  but providing a state 
where they predestined to fail isn't exactly great.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]