From xemacs-m  Fri Aug 22 18:48:31 1997
Received: from cdc.noaa.gov (manager.Colorado.EDU [128.138.218.210])
	by xemacs.org (8.8.5/8.8.5) with SMTP id SAA10836
	for <xemacs-beta@xemacs.org>; Fri, 22 Aug 1997 18:48:31 -0500 (CDT)
Received: from suomi by cdc.noaa.gov (SMI-8.6/SMI-SVR4)
	id RAA14262; Fri, 22 Aug 1997 17:48:34 -0600
Received: by suomi (SMI-8.6) id RAA06935; Fri, 22 Aug 1997 17:48:33 -0600
To: XEmacs beta-list <xemacs-beta@xemacs.org>
Subject: [19.16-b90] INTERNAL EMACS BUGlet (opaque, size=4)
Organization: CIRES, University of Colorado
X-Attribution: mb
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Mark Borges <mdb@cdc.noaa.gov>
Date: 22 Aug 1997 17:48:32 -0600
Message-ID: <vkwwldwzhr.fsf@cdc.noaa.gov>
Lines: 51
X-Mailer: Gnus v5.4.65/XEmacs 19.16(beta90)

[ I'm pretty sure this occurs in XEmacs-20.2 as well. I haven't checked
the latest 20.3 betas, though. ]

Despite the subject line, this is not major (as nothing bad happens,
other than the incessant beeping that ensues and annoys my co-workers
;-). 

I'm consistently seeing this error in the minibuffer,

------------------------------
unrecognized selection-conversion type: nil, #<INTERNAL EMACS BUG (opaque, size=4) 0x8befa0> 
------------------------------

which is apparently coming from src/opaque.c, but which, according to
the comment, shouldn't happen:

------------------------------
/* Should never, ever be called. (except by an external debugger) */
static void                                                         
print_opaque (Lisp_Object obj, Lisp_Object printcharfun, int escapeflag)
{                                                                       
  char buf[200];
  if (INTP (XOPAQUE (obj)->size_or_chain))
    /* sprintf (buf, "#<INTERNAL EMACS BUG (opaque, size=%d) 0x%x>",
             (EMACS_INT) XOPAQUE_SIZE (obj),                     
             (EMACS_INT) XPNTR (obj)); */   

------------------------------

I can trigger it by,

  (1) opening a Citrix winframe window on a windowsNT-3.51 server;
  (2) starting up the evil empire's word processor, and selecting some
      text;
  (3) return to the XEmacs-19.16 frame and select some text
  (4) as the cursor crosses the window edge from the X11 fvwm root
      screen to the winframe window, XEmacs beeps and prints out the
      above in the minibuffer.

Does this make any sense? If it "should never, ever be called", who is
calling it?

I could run this under gdb as well (I think) if someone wants to
investigate it in more depth.

Other than that, 19.16-b90 seems fine. I even dropped in gnus-5.4.65,
and haven't found any problem using it all day. I'll try to remember
to send a formal build report in shortly...

-- 
  -mb-

