Epoch 3.2 problems under HPUX

Thread View: gnu.epoch.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Neil Dixon Tue, 19 Feb 1991 07:49

#2203

Author: Neil Dixon
Date: Tue, 19 Feb 1991 07:49

31 lines
1620 bytes

When using Epoch 3.2 under HPUX 7.0 on an HP 835, I often get the following
message on pressing a mouse button

Wrong type argument: buttonp, #<EMACS BUG: ILLEGAL DATATYPE(#o3777777777767> 
save your buffers immediately and please report this bug.

This seems to occur at quite random times, which makes me suspect problems
in the underlying C code, rather than in the lisp code for handling the
button.  I've also observed that when I attempt a duplicate-screen, I get
the error

Invalid type for conversion.

When attempting to debug what happens here, I find that sometime during the
execution of the lisp, the value of wm-protocol-list gets changed from

(#<X-Atom 82>), 

to 

(#<EMACS BUG: ILLEGAL DATATYPE (#o37777777766) Save your buffers immediately
and please report this bug>)


Anybody know whats happening, and hopefully how to fix it.

Neil Dixon <neil@yc.estec.nl> UUCP:...!mcvax!esatst!neil, BITNET: NDIXON@ESTEC
Thermal Control & Life Support Division (YC) 
European Space Research and Technology Centre (ESTEC),
Noordwijk, The Netherlands.

Re: Epoch 3.2 problems under HPUX

#2204

Author: Alan M. Carroll
Date: Tue, 19 Feb 1991 14:37

31 lines
2076 bytes

In article <9102190752.AA24995@yc1.yc.estec.nl>, neil@yc.estec.nl (Neil Dixon) writes:
> 
> When using Epoch 3.2 under HPUX 7.0 on an HP 835, I often get the following
> message on pressing a mouse button
> 
> Wrong type argument: buttonp, #<EMACS BUG: ILLEGAL DATATYPE(#o3777777777767> 
> save your buffers immediately and please report this bug.

This is a bug we inherited from GNU Emacs. The problem is in the
m-hp9000s800.h file. The definitions for XMARKBIT and XSETMARKBIT are
wrong. The definitions around line 137 should look like:

/* The standard definitions of these macros would work ok,
   but these are faster because the constants are short. */
   

#define XUINT(a) (((unsigned)(a) << INTBITS-VALBITS) >> INTBITS-VALBITS)

#define XSET(var, type, ptr) \
   ((var) = ((int)(type) << VALBITS) + (((unsigned) (ptr) << INTBITS-VALBITS) >> INTBITS-VALBITS))

#define XSETINT(a, b)  XSET(a, XTYPE(a), b)
#define XSETUINT(a, b) XSET(a, XTYPE(a), b)
#define XSETPNTR(a, b) XSET(a, XTYPE(a), b)
#define XMARKBIT(a) ((a) < 0)
#define XSETMARKBIT(a,b) ((a) = ((b) ? (a)|MARKBIT : (a) & ~MARKBIT))

-- 
Alan M. Carroll                "I hate shopping with the reality-impaired"
Epoch Development Team                 - Susan
CS Grad / U of Ill @ Urbana    ...{ucbvax,pur-ee,convex}!cs.uiuc.edu!carroll

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads