From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: maxim@tensilica.com, jimb@codesourcery.com, gdb@sourceware.org,
marc@tensilica.com, pmac@tensilica.com,
ross@tensilica.com
Subject: Re: Understanding GDB frames
Date: Wed, 23 May 2007 07:00:00 -0000 [thread overview]
Message-ID: <ups4sja8j.fsf@gnu.org> (raw)
In-Reply-To: <18003.24582.929104.488280@kahikatea.snap.net.nz> (message from Nick Roberts on Wed, 23 May 2007 09:26:30 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Wed, 23 May 2007 09:26:30 +1200
> Cc: Jim Blandy <jimb@codesourcery.com>, gdb@sourceware.org, Marc Gauthier <marc@tensilica.com>, Pete MacLiesh <pmac@tensilica.com>, Ross Morley <ross@tensilica.com>
>
> > I suggest we improve gdb documentation in the way that, when
> > we don't have time to describe things properly, we at
> > least put a reference to a corresponding GDB-mailing-list
> > discussion.
>
> Eli is the maintainer, but I think the documentation should be self contained.
100% agreement.
> Perhaps you should regard mailing-list as another form of documentation.
If some discussion in the mailing list should find its way to the
manuals, I hope someone who is interested in improving the docs will
write it up and submit for inclusion; I promise to review and approve
such additions ASAP. I could also offer help in adding Texinfo markup
to an otherwise pure-ASCII text, if the author doesn't feel like
writing Texinfo.
next prev parent reply other threads:[~2007-05-23 7:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 22:24 Maxim Grigoriev
2007-05-21 23:28 ` Ross Morley
2007-05-22 2:05 ` Nick Roberts
2007-05-22 2:31 ` Daniel Jacobowitz
2007-05-22 2:51 ` Nick Roberts
2007-05-22 10:58 ` Daniel Jacobowitz
2007-05-22 8:40 ` Ross Morley
2007-05-22 16:10 ` Marc Gauthier
2007-05-22 16:36 ` Daniel Jacobowitz
2007-05-22 18:14 ` Vladimir Prus
2007-05-22 18:33 ` Jim Ingham
2007-05-22 18:36 ` Daniel Jacobowitz
2007-05-23 21:45 ` Jim Blandy
2007-05-22 17:20 ` Ross Morley
2007-05-22 20:24 ` Nick Roberts
2007-05-22 21:12 ` Maxim Grigoriev
2007-05-22 1:40 ` Joel Brobecker
2007-05-22 2:29 ` Daniel Jacobowitz
2007-05-22 18:37 ` Jim Blandy
2007-05-22 19:17 ` Maxim Grigoriev
2007-05-22 20:25 ` Nick Roberts
2007-05-22 20:33 ` Ross Morley
2007-05-22 20:45 ` Maxim Grigoriev
2007-05-22 21:26 ` Nick Roberts
2007-05-23 7:00 ` Eli Zaretskii [this message]
2007-05-23 10:48 ` Daniel Jacobowitz
2007-05-23 12:44 ` Eli Zaretskii
2007-05-22 23:56 ` Jim Blandy
2007-05-23 1:01 ` Maxim Grigoriev
2007-05-23 2:24 ` Daniel Jacobowitz
2007-05-23 16:37 ` Maxim Grigoriev
2007-05-23 0:05 ` Jim Blandy
2007-05-23 0:17 ` Ross Morley
2007-05-23 0:32 ` Jim Blandy
2007-05-23 2:24 ` Ross Morley
2007-05-23 21:52 ` Jim Blandy
2007-05-24 0:05 ` Ross Morley
2007-05-24 1:24 ` Ross Morley
2007-05-24 21:56 ` Jim Blandy
2007-05-23 0:17 ` Daniel Jacobowitz
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=ups4sja8j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=marc@tensilica.com \
--cc=maxim@tensilica.com \
--cc=nickrob@snap.net.nz \
--cc=pmac@tensilica.com \
--cc=ross@tensilica.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