From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] PROBLEMS: Stack backtraces
Date: Fri, 26 Mar 2004 18:08:00 -0000 [thread overview]
Message-ID: <20040326180814.GB21603@nevyn.them.org> (raw)
In-Reply-To: <8011-Fri26Mar2004195947+0300-eliz@gnu.org>
On Fri, Mar 26, 2004 at 07:59:48PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 26 Mar 2004 12:11:50 -0500
> > From: Andrew Cagney <cagney@gnu.org>
> >
> > The attached updates the PROBLEMS: Stack backtraces section so that it
> > is more current.
> >
> > comments, it's intended for 6.1
>
> I think these additions are very useful, so I think they should be in
> v6.1.
>
> A couple of minor gotchas:
>
> > +GDB's code base is being been updated to use a new backtrace
> > +mechanism. This mechanism makes possible the support of new features
>
> I think "This mechanism makes possible to support new features" is
> better.
Except that's not valid English - do you mean "makes it possible to"?
Also, "is being been".
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-26 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 17:11 Andrew Cagney
2004-03-26 18:02 ` Eli Zaretskii
2004-03-26 18:08 ` Daniel Jacobowitz [this message]
2004-03-26 18:35 ` Eli Zaretskii
2004-03-26 18:10 ` Daniel Jacobowitz
2004-03-26 18:32 ` Eli Zaretskii
2004-03-28 19:57 ` Andrew Cagney
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=20040326180814.GB21603@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.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