Thanks, Wenji. I already knew I'd fixed the bug. ;-) The bug in question only ever affected a 32-bit process on a 64-bit kernel. That test as written hits the assert when built for x86_64. Changes to %cs or %ss have no effect on a 64-bit process, so the traced process does not crash as a 32-bit process with a bad %cs value should. It is still a bit useful to run this test built for 64-bit, since it exercises some of the other corners of the same code paths. I've adjusted the test.
Thanks, Roland