Fix test addresses to use uintptr_t instead of u_int64_t.

Fix test addresses to use uintptr_t instead of u_int64_t.

When a variable is used to set (and lookup) MappingInfo's "start_addr"
field, it needs to match types -- which is "uintptr_t".  When Chrome OS
updated the 'make' that's used for building, the 32-bit "char *" had
sign-extended when cast up to a u_int64_t -- maybe because pointers were
unsigned before and then changed to be signed -- and that caused the address
lookup to fail.

BUG=chromium-os:25355
TEST=Ran Breakpad unittests

[Michael Krebs]

This fixes a unittest that failed when building for Chrome OS.  Assuming this
change is okay could someone submit this, as I'm not a submitter?

[Ben Chan]

On 2012/01/27 04:21:14, Michael Krebs wrote:
> This fixes a unittest that failed when building for Chrome OS.  Assuming this
> change is okay could someone submit this, as I'm not a submitter?

LGTM.

[Ben Chan]

On 2012/01/27 05:09:11, Ben Chan wrote:
> On 2012/01/27 04:21:14, Michael Krebs wrote:
> > This fixes a unittest that failed when building for Chrome OS.  Assuming
this
> > change is okay could someone submit this, as I'm not a submitter?
> 
> LGTM.

Mike, I committed the CL for you (@r908).

[Ben Chan]

On 2012/01/27 05:24:49, Ben Chan wrote:
> On 2012/01/27 05:09:11, Ben Chan wrote:
> > On 2012/01/27 04:21:14, Michael Krebs wrote:
> > > This fixes a unittest that failed when building for Chrome OS.  Assuming
> this
> > > change is okay could someone submit this, as I'm not a submitter?
> > 

Please close this issue.
> > LGTM.
> 
> Mike, I committed the CL for you (@r908).