constraints_parser.c:88: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘ulint’
constraints_parser.c: In function ‘check_fields_sizes’:
constraints_parser.c:130: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 4 has type ‘ulint’
constraints_parser.c: In function ‘ibrec_init_offsets_new’:
constraints_parser.c:231: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c: In function ‘ibrec_init_offsets_old’:
constraints_parser.c:265: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c:288: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c: In function ‘check_for_a_record’:
constraints_parser.c:320: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’
constraints_parser.c:324: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o page_parser page_parser.c lib/tables_dict.o lib/libut.a
page_parser.c: In function ‘process_ibpage’:
page_parser.c:42: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’
page_parser.c:46: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’
page_parser.c: In function ‘process_ibfile’:
page_parser.c:72: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’

at first I ignored that but when i made the page_parser with my ibdata1 file and got all the pages whe i used the constrains_parsers i am getting empty rows totally empty or segmentation faul, do you know if the warning are causing the error, or what could i made wrong? Thanks in advance Alfredo Herrejon

Well, sometimes sh*t happens and it is nice to have such tool ready

I should only note what “Undelete” and “Dropped Tables” is only one application of this toolset. FileSystem corruption or bad Innodb crashes are also possible applications.