> I could not reproduce this.  If you can, would you please try to
> figure out what caused the trap?  (Use ddb to get the arguments
> and actual instruction pointer offset where the trap happens.)

It happened twice before I reported it, but I just tried it again and
no panic.

I will get the whole trace to you if it happens again.