> I can fix valgrind to initialise %cs, %ds and %ss at startup to match > the system, which will stop the segv but it will then assert as the > segment register will point at a GDT entry that valgrind can't > handle currently. Thank! Assertion is better than SEGV. > value. Given that, an instruction with an explicit %ds qualification > is the same as one with no segment qualification except that it > probably executes much slower... Yesterday I add library into project, checked program under valgrind and = received SEGV. It was strange for me because before valgrind produce = assertion messages while running incorrect programs. Letter was sent = only for bug report. I was surprised looking into library code and rewrote it :) Dmytry Dyachenko http://CryptoPro.ru |