Add support for more param traits in ipc fuzzer

Add support for more param traits

R=mbarbella@chromium.org
TBR=tsepez@chromium.org
BUG=450268
Committed: https://crrev.com/eb016f0d649ae395fa7d2d7d8633c788eaa6985a
Cr-Commit-Position: refs/heads/master@{#316902}

[Martin Barbella, 2015-02-18 20:08:02]

lgtm

https://codereview.chromium.org/932103003/diff/1/tools/ipc_fuzzer/mutate/gene...
File tools/ipc_fuzzer/mutate/generate.cc (right):

https://codereview.chromium.org/932103003/diff/1/tools/ipc_fuzzer/mutate/gene...
tools/ipc_fuzzer/mutate/generate.cc:1045: info.type =
(blink::WebCursorInfo::Type)(RandInRange(44));
Can we use the last type + 1 here instead of this? It's probably also worth
investigating or at least leaving a TODO to see if we can define this properly
using the IPC_ENUM_TRAITS_MAX_VALUE macro so that we don't need this hack.

[Tom Sepez, 2015-02-18 20:17:11]

lgtm

https://codereview.chromium.org/932103003/diff/1/tools/ipc_fuzzer/mutate/gene...
File tools/ipc_fuzzer/mutate/generate.cc (right):

https://codereview.chromium.org/932103003/diff/1/tools/ipc_fuzzer/mutate/gene...
tools/ipc_fuzzer/mutate/generate.cc:1045: info.type =
(blink::WebCursorInfo::Type)(RandInRange(44));
On 2015/02/18 20:08:02, mbarbella wrote:
> Can we use the last type + 1 here instead of this? It's probably also worth
> investigating or at least leaving a TODO to see if we can define this properly
> using the IPC_ENUM_TRAITS_MAX_VALUE macro so that we don't need this hack.

We'd like to stick out-of-range values here, too.

[Martin Barbella, 2015-02-18 20:18:59]

On 2015/02/18 20:17:11, Tom Sepez wrote:
> lgtm
> 
>
https://codereview.chromium.org/932103003/diff/1/tools/ipc_fuzzer/mutate/gene...
> File tools/ipc_fuzzer/mutate/generate.cc (right):
> 
>
https://codereview.chromium.org/932103003/diff/1/tools/ipc_fuzzer/mutate/gene...
> tools/ipc_fuzzer/mutate/generate.cc:1045: info.type =
> (blink::WebCursorInfo::Type)(RandInRange(44));
> On 2015/02/18 20:08:02, mbarbella wrote:
> > Can we use the last type + 1 here instead of this? It's probably also worth
> > investigating or at least leaving a TODO to see if we can define this
properly
> > using the IPC_ENUM_TRAITS_MAX_VALUE macro so that we don't need this hack.
> 
> We'd like to stick out-of-range values here, too.

Good point. Since they're not validating it there's no reason to worry about it
during generation.

[inferno, 2015-02-18 20:52:07]

New patchsets have been uploaded after l-g-t-m from
mbarbella@chromium.org,tsepez@chromium.org

[inferno, 2015-02-18 21:06:39]

Patchset #2 (id:20001) has been deleted

[Martin Barbella, 2015-02-18 21:35:04]

lgtm

[inferno, 2015-02-18 21:35:10]

The CQ bit was checked by inferno@chromium.org

[commit-bot: I haz the power, 2015-02-18 21:35:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/932103003/40001

[commit-bot: I haz the power, 2015-02-18 22:11:20]

Committed patchset #2 (id:40001)

[commit-bot: I haz the power, 2015-02-18 22:12:06]

Patchset 2 (id:??) landed as
https://crrev.com/eb016f0d649ae395fa7d2d7d8633c788eaa6985a
Cr-Commit-Position: refs/heads/master@{#316902}