Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: justin.lebar@gmail.com, gdb-patches@sourceware.org
Subject: Re: [Patch] Bug 8287: Skip uninteresting functions while debugging
Date: Fri, 18 Jun 2010 20:58:00 -0000	[thread overview]
Message-ID: <83k4pwgiut.fsf@gnu.org> (raw)
In-Reply-To: <4C1BCAF5.9000603@vmware.com>

> Date: Fri, 18 Jun 2010 12:37:25 -0700
> From: Michael Snyder <msnyder@vmware.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> Justin Lebar wrote:
> > This adds support for a "blacklist" which contains files and functions
> > which are skipped while single-stepping.  This patch also fixes bug
> > 11614: decode_variable() in linespec.c does not obey its contract
> 
> Greetings, welcome, and thanks for your submission.
> 
> There are a few problems, mostly things we usually encounter with new
> contributors.
> 
> First, I can't apply your patch.  There are line wrappings, character
> substitutions when I save the email, and so on.  Would you mind trying
> to send the patch as a plain text attachment?
> 
> Second, we need a ChangeLog entry.  See gdb/ChangeLog for examples
> of how those are composed and formatted.
> 
> Finally, have you got a copyright assignment filed?

If this contribution is accepted, we will also need a suitable patch
for the manual, to describe the new feature and commands, and a NEWS
entry.

Thanks.


  reply	other threads:[~2010-06-18 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 18:56 Justin Lebar
2010-06-18 19:37 ` Michael Snyder
2010-06-18 20:58   ` Eli Zaretskii [this message]
2010-06-20  7:03 ` Hui Zhu
2010-06-25 21:57 ` Tom Tromey
2010-06-28 17:44   ` Justin Lebar
2010-07-20 21:03     ` Tom Tromey
2010-07-23 19:50       ` Justin Lebar
2011-04-25 19:35         ` Justin Lebar
2011-05-16 21:04           ` Justin Lebar

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=83k4pwgiut.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=justin.lebar@gmail.com \
    --cc=msnyder@vmware.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