From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] reimplement AIX shared-lib support (v3)
Date: Tue, 07 May 2013 08:42:00 -0000 [thread overview]
Message-ID: <20130507084225.GJ5278@adacore.com> (raw)
In-Reply-To: <5187C8A5.50200@redhat.com>
> Yay, you're my hero! :-)
:-D
> > gdb/ChangeLog:
> >
> > * features/library-list-aix.dtd: New file.
>
> I think we should document this in the manual? We
> document library-list-svr4 there too.
Yes, you are right. Upon trying to document it, and looking at
how the other XML formats are described in the manual, I realized
that maybe it would be better if the XML used library-list-aix
instead of just library-list. It would be more consistent, I think,
with what is done for instance with SVR4, but also avoid any
confusion with the library-list. WDYT? I'll document what's
currently checked in, but it's very easy to change.
> > + /* Debug this file's internals. */
> > + add_setshow_boolean_cmd ("aix-solib", class_maintenance,
> > + &solib_aix_debug, _("\
> > +Control the debugging traces for the solib-aix module."), _("\
> > +Show whether solib-aix debugging traces are enabled."), _("\
> > +When on, solib-aix debugging traces are enabled."),
> > + NULL,
> > + show_solib_aix_debug,
> > + &setdebuglist, &showdebuglist);
>
> This too. :-)
I started with the easy one :-)
http://www.sourceware.org/ml/gdb-patches/2013-05/msg00178.html
--
Joel
next prev parent reply other threads:[~2013-05-07 8:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 14:20 Joel Brobecker
2013-05-06 15:13 ` Pedro Alves
2013-05-07 8:42 ` Joel Brobecker [this message]
2013-05-07 8:56 ` Pedro Alves
2013-05-07 10:10 ` Joel Brobecker
2013-05-07 10:14 ` Joel Brobecker
2013-05-07 13:45 ` Luis Machado
2013-05-07 14:15 ` Tom Tromey
2013-05-07 14:17 ` Luis Machado
2013-05-07 14:28 ` Joel Brobecker
2013-05-07 14:31 ` Luis Machado
2013-05-07 14:45 ` Luis Machado
2013-05-08 6:15 ` Joel Brobecker
2013-05-07 15:24 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130507084225.GJ5278@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox