From: Richard Earnshaw <rearnsha@arm.com>
To: Girish Shilamkar <girish@linsyssoft.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Read arm core files
Date: Wed, 15 Feb 2006 11:51:00 -0000 [thread overview]
Message-ID: <1140004253.28394.32.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <1140001485.3359.12.camel@krypton>
On Wed, 2006-02-15 at 11:04, Girish Shilamkar wrote:
> Hi,
> The patch enables gdb to read arm core files.
> -Girish.
Girish,
This needs some work yet before it can be accepted.
BTW, do you have a copyright assignment in place? If not, then we will
need one before we can proceed any further.
Finally, please make sure your patches are against the most recent
version of CVS rather than a release. We don't incorporate new code
onto existing releases.
R.
2006-02-15 Girish Shilamkar <girish@linsyssoft.com>
* arm-linux-tdep.c Core file handler has been added.
* config/arm/linux.mt Compiles corelow.c required for
deprecated_add_core_fns
Please take a closer look at existing ChangeLog entries and try to copy
the style there. All entries are of the form
* <file modified>: (<function modified>) Sentence
describing change, ending with full stop.
+/* Following enums used to implement the core file support. */
Two spaces at the end of a sentence, even if it ends the entire
comment. Your sentence isn't grammatically correct either: "The
following enums are used to implement core file support."
+enum {
+ ELF_NGREG = 18, /* core reg size is 72 */
All comments start with a capital letter.
void
+arm_linux_supply_gregset (char *buf)
All functions must have a comment that precedes them describing what
they do -- even in cases like this where it is fairly obvious.
+ regcache_raw_supply (current_regcache, FP0_REGNUM + regi, buf + 8 * regi);
Watch out for line length. Wrap your code *before* you reach column 80.
+ warning ("wrong size gregset struct in core file");
You need to take care of i18n here. Wrap your strings thus _("My string
for translation").
next prev parent reply other threads:[~2006-02-15 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 11:05 Girish Shilamkar
2006-02-15 11:51 ` Richard Earnshaw [this message]
2006-02-15 13:05 ` Girish Shilamkar
2006-02-15 11:55 ` Mark Kettenis
2006-02-24 14:01 ` Girish Shilamkar
2006-02-24 22:41 ` Mark Kettenis
2006-03-08 15:38 ` Girish Shilamkar
2006-03-13 20:21 ` Girish Shilamkar
2006-03-14 3:36 ` Daniel Jacobowitz
[not found] ` <1142260008.2867.13.camel@krypton>
2006-03-14 15:44 ` Daniel Jacobowitz
[not found] ` <20060313202419.GB24419@nevyn.them.org>
2006-03-15 14:47 ` Girish Shilamkar
2006-03-15 16:11 ` Daniel Jacobowitz
2006-02-25 4:38 ` Randolph Chung
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=1140004253.28394.32.camel@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=girish@linsyssoft.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