From: Eli Zaretskii <eliz@gnu.org>
To: Michael Eager <eager@eagercon.com>
Cc: jimb@codesourcery.com, gdb@sources.redhat.com
Subject: Re: GDB Documentation and Request for Help
Date: Sat, 31 Mar 2007 08:29:00 -0000 [thread overview]
Message-ID: <u3b3l95qa.fsf@gnu.org> (raw)
In-Reply-To: <460D7DC7.1050803@eagercon.com> (message from Michael Eager on Fri, 30 Mar 2007 14:14:47 -0700)
> Date: Fri, 30 Mar 2007 14:14:47 -0700
> From: Michael Eager <eager@eagercon.com>
> CC: gdb@sources.redhat.com
>
> > (Having worked on both, I think the new frame system is *much* nicer
> > to work with, and more reliable. So your efforts won't be wasted.)
>
> I'm sure that it is. It's just not documented.
Yes, unfortunately. However, if, after you figure that out, you
publish your findings and understandings, I promise to make a manual
section out of what you write and add that to gdbint.texinfo.
Thanks in advance.
next prev parent reply other threads:[~2007-03-31 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 17:20 Michael Eager
2007-03-30 18:08 ` Jim Blandy
2007-03-30 18:27 ` Michael Eager
2007-03-30 18:41 ` Daniel Jacobowitz
2007-03-30 21:02 ` Jim Blandy
2007-03-30 21:14 ` Michael Eager
2007-03-31 8:29 ` Eli Zaretskii [this message]
2007-04-04 14:57 ` Dave Korn
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=u3b3l95qa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@codesourcery.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