From: Giuseppe MONTALTO <giuseppe.montalto@st.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] new MI command for pattern filling of memory regions
Date: Fri, 11 May 2012 16:06:00 -0000 [thread overview]
Message-ID: <76FE3225DF13124EA2D05B290B624C95E65FECE56F@SAFEX1MAIL1.st.com> (raw)
In-Reply-To: <87397624b9.fsf@fleche.redhat.com>
Thanks,
my answers are interleaved below.
> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com]
> Sent: Friday, May 11, 2012 4:14 PM
> To: Giuseppe MONTALTO
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH] new MI command for pattern filling of memory
> regions
>
> The indentation is wrong here and elsewhere in the patch.
> There are missing spaces as well.
> See the GNU Coding Standards for details.
I'll try to better format the code.
>
> I don't think the cast here, or other casts in the patch, are
> necessary.
Consider them gone.
>
> Giuseppe> + /* pattern is made of less bytes than count:
> Giuseppe> + repeat pattern to fill memory. */
> Giuseppe> + data = xmalloc (count/len);
>
> This allocates count/len bytes...
>
> Giuseppe> + steps = count/len;
> Giuseppe> + for (j = 0; j < steps; j++)
> Giuseppe> + {
> Giuseppe> + for (i = 0; i < len; ++i)
> Giuseppe> + {
> Giuseppe> + int x;
> Giuseppe> + sscanf (cdata + i * 2, "%02x", &x);
> Giuseppe> + data[i + j * len] = (gdb_byte)x;
>
> ... but writes 'count' bytes.
you're right; I was supposed to allocate 'count' bytes.
Incidentally, there's a worse error there:
is that I'm counting the cycles basing on the result of an integer
division, hence not taking into account the spare bytes!
I'll fix that too...
Giuseppe
next prev parent reply other threads:[~2012-05-11 16:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:18 Giuseppe MONTALTO
2012-05-09 16:30 ` Tom Tromey
2012-05-09 18:11 ` Tom Tromey
2012-05-10 11:41 ` Giuseppe MONTALTO
2012-05-10 13:57 ` Tom Tromey
2012-05-11 8:53 ` Giuseppe MONTALTO
2012-05-11 14:36 ` Tom Tromey
2012-05-11 16:06 ` Giuseppe MONTALTO [this message]
2012-05-25 14:35 ` Giuseppe MONTALTO
2012-06-12 9:07 ` Giuseppe MONTALTO
2012-06-12 10:01 ` Abid, Hafiz
2012-06-12 14:13 ` Giuseppe MONTALTO
2012-06-12 14:22 ` [PATCH] enhancement of mi_cmd_data_write_memory_bytes for filling memory regions (was [PATCH] new MI command for pattern filling of memory regions) Giuseppe MONTALTO
2012-09-14 16:30 ` Tom Tromey
2012-09-18 15:19 ` Giuseppe MONTALTO
2012-09-26 20:44 ` Tom Tromey
2012-09-27 15:27 ` Giuseppe MONTALTO
2012-09-28 20:07 ` Tom Tromey
2012-10-01 9:29 ` Giuseppe MONTALTO
2012-10-17 20:59 ` Tom Tromey
2012-10-18 13:40 ` Giuseppe MONTALTO
2012-10-18 15:41 ` Pedro Alves
2012-10-18 16:16 ` Giuseppe MONTALTO
2012-10-18 16:28 ` [+docs] " Pedro Alves
2012-10-18 17:31 ` Eli Zaretskii
2012-10-18 17:30 ` Eli Zaretskii
2012-10-19 14:12 ` Giuseppe MONTALTO
2012-10-19 16:34 ` Eli Zaretskii
2012-10-19 16:56 ` Pedro Alves
2012-10-22 7:02 ` Giuseppe MONTALTO
2012-11-08 20:37 ` Tom Tromey
2012-11-09 8:59 ` Giuseppe MONTALTO
2012-11-12 16:52 ` Tom Tromey
2012-11-13 10:50 ` Giuseppe MONTALTO
2012-11-13 21:19 ` Tom Tromey
2012-10-18 16:38 ` Giuseppe MONTALTO
2012-10-18 19:45 ` 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=76FE3225DF13124EA2D05B290B624C95E65FECE56F@SAFEX1MAIL1.st.com \
--to=giuseppe.montalto@st.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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