Bug #56461 for File-BSED: gbsed ?

hi ! something like that doesnt seem to work w gbsed .... should it ? gbsed -s 0x554889e548895dd84c8965e0bb12000000 -r 0xb800000000c390904c8965e0bb12000000 binary binary.patched is it because of the large hex "string" ? gbsed reports 1 match but somehow the search / replace seems not to be done in place, the file lengths differ, too ! :( :( :( ------ do i have to use the '0x' ?? is the hex mode not given anyway by using -s/r (in difference to -S/R) ? ------ btw are the wildcards working in hex mode too ? would be nice to be able to do this : gbsed -s 0xe897?12 binary ---> for 1 byte gbsed -s 0xe897?*12 binary ---> for more than 1 byte (maybe too complicated?) ------ and... when using this : gbsed -s 0xe8970012 binary it would be nice to get the offset where the match was found ! and maybe even a dump +/- some bytes ------ keep upt the work !! :) and maybe check about the first thing. this renders gbsed useless for me. steven