Can you produce a /sbin/cryptsetup that is compiled with -g and without optimization, and not stripped? In otherwords, theoretically ready for debugging. Then test if the problem can be reproduced with that executable. While you're at it, make it so that you can easily add/remove debug output lines to the code and recompile reinstall. If you can reproduce it that way, you can start to add debug output lines to the code to narrow down where things start to differ; ie, does the change happen in a function of one of the libraries, or is the fault in cryptsetup? -- Carlo Wood <carlo@xxxxxxxxxx> --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
