drag-n-drop core dump

I am running XEmacs 21.0 Toggenburg on my SGI box, and decide that since I have an NT on the corner of my desk, I should run Exceed on it and get another monitor for XEmacs. I normally have no problem running on multiple displays. I will dial in from home and attach/detach that display. However, something is going on, and maybe it's Exceed, but it seems weird. The first weirdness is that every time an XEmacs frame on my SGI would gain focus, it would pop up a "*MIME-Drop data*" buffer. I tracked that down by replacing the `experimental-dragdrop-drop-functions' with my own function that throws an error. Here is the backtrace: It appears that XEmacs thinks that it is getting a drop event, even though it is a normal window-enter. Here are the event and object from the callback: event: #<misc-user-event (dragdrop-drop-dispatch (dragdrop-MIME (("application/octet-stream") "8bit" "")))>, object: (dragdrop-MIME ((application/octet-stream) 8bit )) Of course, it gets worse. When I then close the XEmacs frame on the NT, the next time I move focus into an SGI frame, I get the following stack trace on a SEGV. Of course, this is all running -vanilla. Does anybody have a similar problem? Does anyone run a similar configuration and not have this problem? -- Colin