search for: print_sysappend

...a byte in the range of 128 to 255 in one of the SYSAPPEND strings has to survive. (But why did "unsigned char c;" not solve the problem for poma ? Why did it work with gcc 4.9 ?) One should create a possibility to dump the SYSAPPEND strings. There is a function ./core/sysappend.c:void print_sysappend(void) but i cannot spot any occasion where it gets called. Have a nice day :) Thomas

...particular machine suffers some sort of partial fault that corrupts the appropriate string to contain a character between 128 and 255, that would explain this quite easily. > One should create a possibility to dump the SYSAPPEND > strings. There is a function > ./core/sysappend.c:void print_sysappend(void) > but i cannot spot any occasion where it gets called. A simple COM32. -- -Gene

...255 in one of the SYSAPPEND > strings has to survive. (But why did "unsigned char c;" > not solve the problem for poma ? Why did it work with gcc 4.9 ?) > > One should create a possibility to dump the SYSAPPEND > strings. There is a function > ./core/sysappend.c:void print_sysappend(void) > but i cannot spot any occasion where it gets called. > > > Have a nice day :) I suppose it's possible we were testing with different syslinux configurations. I was building Fedora Rawhide live images as my test, with the volume label '20150702-syslinux-x86_64'. T...

...{ .iget = xfs_iget, .next_extent = xfs_next_extent, .readlink = xfs_readlink, + .fs_uuid = NULL, }; diff --git a/core/include/core.h b/core/include/core.h index 127ac65..4af037e 100644 --- a/core/include/core.h +++ b/core/include/core.h @@ -81,6 +81,7 @@ extern void print_sysappend(void); extern const char *sysappend_strings[SYSAPPEND_MAX]; extern uint32_t SysAppends; extern void sysappend_set_uuid(const uint8_t *uuid); +extern void sysappend_set_fs_uuid(void); void __cdecl core_intcall(uint8_t, const com32sys_t *, com32sys_t *); void __cdecl core_farcall(uint32_t, con...