This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [5.2.1] quiet warnings for gdbreplay.c
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gdb-patches at sources dot redhat dot com, eliz at gnu dot org
- Cc: cagney at redhat dot com
- Date: Sat, 21 Jun 2003 14:07:38 -0400
- Subject: Re: [5.2.1] quiet warnings for gdbreplay.c
- References: <20020627204720.A13445@dragon.nuxi.com> <3D1C8AEF.5020508@ges.redhat.com> <20020628180820.GA9115@nevyn.them.org> <3D1CD337.2010205@ges.redhat.com> <20020628213904.GA15095@nevyn.them.org> <3D2B5212.3020302@ges.redhat.com> <20030621174002.GB14161@nevyn.them.org>
On Sat, Jun 21, 2003 at 01:40:02PM -0400, Daniel Jacobowitz wrote:
> On Tue, Jul 09, 2002 at 05:13:54PM -0400, Andrew Cagney wrote:
> > >Then do we want a separate gdb/gdbint/ directory for this? I strongly
> > >prefer that headers shared between GDB and other directories be clearly
> > >marked and separated. That'd give me a place to move
> > >gdb_proc_service.h, too.
> >
> > I think it would be easier to just clarify the guidelines for
> > ``gdb_XXXX.h'' files - that they be independant as they are included by
> > GDB and friends.
>
> This has been on my TODO list for almost a year... Andrew, how's this?
Hi Eli,
Since it seems I captured Andrew's and my intent correctly, is this
documentation patch OK?
> 2003-06-21 Daniel Jacobowitz <drow@mvista.com>
>
> * gdbint.texinfo (Coding): Clarify use of gdb_XXX.h headers.
>
> Index: gdbint.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
> retrieving revision 1.154
> diff -u -p -r1.154 gdbint.texinfo
> --- gdbint.texinfo 19 Jun 2003 15:04:05 -0000 1.154
> +++ gdbint.texinfo 21 Jun 2003 17:38:47 -0000
> @@ -5191,7 +5191,11 @@ of @value{GDBN}) must be added to @file{
>
> When @value{GDBN} has a local version of a system header file (ex
> @file{string.h}) the file name based on the POSIX header prefixed with
> -@file{gdb_} (@file{gdb_string.h}).
> +@file{gdb_} (@file{gdb_string.h}). These headers should be relatively
> +independent: they should use only macros defined by @file{configure},
> +the compiler, or the host; they should include only system headers; they
> +should refer only to system types. They may be shared between multiple
> +programs, e.g.@: @value{GDBN} and @sc{gdbserver}.
>
> For other files @samp{-} is used as the separator.
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer