Re: [Xen-devel] [xen-unstable bisection] complete build-i386

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

xen.org writes ("[xen-unstable bisection] complete build-i386"):
> branch xen-unstable
> xen branch xen-unstable
> job build-i386
> test xen-build
> 
> Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> Tree: xen git://xenbits.xen.org/xen.git
> 
> *** Found and reproduced problem changeset ***
> 
>   Bug is in tree:  xen git://xenbits.xen.org/xen.git
>   Bug introduced:  ae763e4224304983a1cde2fbb3d6e0c4d60b2688
>   Bug not present: 266abb240738bb37ccb28623806273c58523f422
> 
> 
>   commit ae763e4224304983a1cde2fbb3d6e0c4d60b2688
>   Author: Dario Faggioli <dario.faggioli@xxxxxxxxxx>
>   Date:   Tue Sep 10 19:54:20 2013 +0200
>   
>       tools/misc: introduce xen-mfndump.
>       
>       A little development and debugging tool, useful when looking
>       for information about MFN to PFN mappings, MFN/PFN mappings
>       in a guest's PTEs, etc.
...

Looking at the logs, this is correct:

cc1: warnings being treated as errors
xen-mfndump.c: In function 'dump_ptes_func':
xen-mfndump.c:236: error: format '%lx' expects type 'long unsigned int', but 
argument 3 has type 'uint64_t'
xen-mfndump.c: In function 'lookup_pte_func':
xen-mfndump.c:305: error: format '%lx' expects type 'long unsigned int', but 
argument 5 has type 'uint64_t'
make[3]: *** [xen-mfndump.o] Error 1

You need to make the types and the printf formats consistent, perhaps
by use of PRIx64 et al.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel