Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!dik
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: comp.unix.ultrix
Subject: Re: DS3100: buggy cc
Message-ID: <8168@boring.cwi.nl>
Date: 6 Jun 89 23:29:43 GMT
References: <1207@ttds.UUCP> <1211@ttds.UUCP>
Organization: CWI, Amsterdam
Lines: 123

(I am not able to reply, hence a followup)

In article <1211@ttds.UUCP> jonasn@ttds.UUCP (Jonas Nygren) writes:
 > do_nextevent()
 > {
 > 	XAnyEvent e;
 > 
 > 	XNextEvent(display, &e);
 > }

Perusing the X sources reveals that the second parameter of XNextEvent
is not of type *XAnyEvent but of type *XEvent (which is a union of
all kinds of events).  Probably an XEvent is larger than an XAnyEvent,
so XNextEvent will scribble somewhat on the stack, and all kind of
things may happen.
-- 
dik t. winter, cwi, amsterdam, nederland
INTERNET   : dik@cwi.nl
BITNET/EARN: dik@mcvax
From dik@boring.cwi.nl  Wed Jun  7 01:26:13 1989
Received: by boring.cwi.nl via EUnet; Wed, 7 Jun 89 01:26:13 +0200 (MET)
Date: Wed, 7 Jun 89 01:26:13 +0200
From: dik@boring.cwi.nl (Dik T. Winter)
Message-Id: <8906062326.AA01677@boring.cwi.nl>
To: draken!ttds!jonasn@kth.uucp
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211@ttds.UUCP>
References: <1207@ttds.UUCP>
Organization: CWI, Amsterdam

In article <1211@ttds.UUCP> you write:
 > do_nextevent()
 > {
 > 	XAnyEvent e;
 > 
 > 	XNextEvent(display, &e);
 > }

Perusing the X sources reveals that the second parameter of XNextEvent
is not of type *XAnyEvent but of type *XEvent (which is a union of
all kinds of events).  Probably an XEvent is larger than an XAnyEvent,
so XNextEvent will scribble somewhat on the stack, and all kind of
things may happen.
-- 
dik t. winter, cwi, amsterdam, nederland
INTERNET   : dik@cwi.nl
BITNET/EARN: dik@mcvax

To: jonasn@ttds.UUCP
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211@ttds.UUCP>
References: <1207@ttds.UUCP>
Organization: CWI, Amsterdam

In article <1211@ttds.UUCP> you write:
 > do_nextevent()
 > {
 > 	XAnyEvent e;
 > 
 > 	XNextEvent(display, &e);
 > }

Perusing the X sources reveals that the second parameter of XNextEvent
is not of type *XAnyEvent but of type *XEvent (which is a union of
all kinds of events).  Probably an XEvent is larger than an XAnyEvent,
so XNextEvent will scribble somewhat on the stack, and all kind of
things may happen.
-- 
dik t. winter, cwi, amsterdam, nederland
INTERNET   : dik@cwi.nl
BITNET/EARN: dik@mcvax

To: mcvax!kth!draken!ttds!jonasn
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211@ttds.UUCP>
References: <1207@ttds.UUCP>
Organization: CWI, Amsterdam

In article <1211@ttds.UUCP> you write:
 > do_nextevent()
 > {
 > 	XAnyEvent e;
 > 
 > 	XNextEvent(display, &e);
 > }

Perusing the X sources reveals that the second parameter of XNextEvent
is not of type *XAnyEvent but of type *XEvent (which is a union of
all kinds of events).  Probably an XEvent is larger than an XAnyEvent,
so XNextEvent will scribble somewhat on the stack, and all kind of
things may happen.
-- 
dik t. winter, cwi, amsterdam, nederland
INTERNET   : dik@cwi.nl
BITNET/EARN: dik@mcvax

To: jonasn@ttds.UUCP
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211@ttds.UUCP>
References: <1207@ttds.UUCP>
Organization: CWI, Amsterdam

In article <1211@ttds.UUCP> you write:
 > do_nextevent()
 > {
 > 	XAnyEvent e;
 > 
 > 	XNextEvent(display, &e);
 > }

Perusing the X sources reveals that the second parameter of XNextEvent
is not of type *XAnyEvent but of type *XEvent (which is a union of
all kinds of events).  Probably an XEvent is larger than an XAnyEvent,
so XNextEvent will scribble somewhat on the stack, and all kind of
things may happen.
-- 
dik t. winter, cwi, amsterdam, nederland
INTERNET   : dik@cwi.nl
BITNET/EARN: dik@mcvax