From: Keith Seitz <keiths@redhat.com>
To: logitech <supriya.rao17@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Integration of timed breakpoints into GDB
Date: Thu, 08 Sep 2011 01:30:00 -0000 [thread overview]
Message-ID: <4E67F9F3.6030206@redhat.com> (raw)
In-Reply-To: <32418104.post@talk.nabble.com>
On 09/07/2011 10:42 AM, logitech wrote:
> Further details about the implementation can be found here
> http://www.youtube.com/watch?v=PAFQlxqI7qs&feature=player_embedded#! GDB
> Timed breakpoint
>
> I would highly appreciate comments and feedback from your side regarding the
> same.
Thank you for submitting your new feature patch.
To help facilitate the review of your patch, I urge you to read through
CONTRIBUTE (found in src/gdb/ or on the gdb web page
http://sourceware.org/gdb/contribute/ ) and make any necessary changes
to your contribution mentioned in that file.
Specifically:
- Generate diffs (for source files) using "-up" options, preferably
against CVS HEAD. Instructions for getting CVS HEAD are on the web page
at http://sourceware.org/gdb/current/ . No need to send diffs for
ChangeLogs and generated files (like gdb/configure).
- Read and follow the GNU coding standards. There is more on this on the
gdb wiki:
http://sourceware.org/gdb/current/onlinedocs/gdbint/Coding-Standards.html .
There is also Joel's excellent "cheat sheet" at
http://sourceware.org/gdb/wiki/JoelsCodingStyleCheatSheet .
- You are not listed in MAINTAINERS, do you and/or your company (if
necessary) have an assignment with the FSF?
- You did not supply any ChangeLog entry(-ies).
- I don't see a test case for this. You should write one. It is mostly a
cut-n-paste job today. Don't be afraid to ask for help. [Hint: start
with any simple test in gdb.base that uses prepare_for_testing.]
- This will require additions to documentation and probably a NEWS entry.
Thank you!
Keith
next prev parent reply other threads:[~2011-09-07 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 23:11 logitech
2011-09-08 1:30 ` Keith Seitz [this message]
2011-09-08 12:57 ` Abhijit Halder
2011-09-08 13:09 ` logitech
2011-09-10 12:46 ` Jan Kratochvil
2011-10-03 17:46 ` 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=4E67F9F3.6030206@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=supriya.rao17@gmail.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