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: [PATCH 06/25] Generate c for feature instead of tdesc


> From: Yao Qi <qiyaoltc@gmail.com>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 14 Jun 2017 17:21:36 +0100
> 
> > But that means the produced file can only be used by rebuilding GDB,
> > doesn't it?  If so, the text should make this clear, I think.
> >
> 
> Yes.  The last sentence is about it, "The created source file is built
> into @value{GDBN}", but I didn't explicitly say GDB needs rebuild.

I think we should say that.

> > (In general, since GDB is a compiled program which cannot easily be
> > modified without rebuilding it, I wonder how useful this feature will
> > be.  But I'll yield to your expertise on that.)
> 
> This command is only used by developers after they add or modify XML
> target descriptions.

Then I think we should say that as well.

> A question in general, do we really need to document these commands,
> which are used for GDB development, in GDB user manual?  These
> commands are "maint print c-tdesc", "maint check xml-descriptions"
> (added by one patch in this series), and "maint selftest".  Can we
> remove them from the user manual?

If we remove them, there will be no place where they are documented,
right?  GDB developers are GDB users as well, e.g. I read the manual
quite a lot.

So I see no reason to remove these commands.  We just need to indicate
when a command makes sense only for GDB developers.

Thanks.


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