DS3100: buggy cc
Dik T. Winter
dik at cwi.nl
Wed Jun 7 09:29:43 AEST 1989
(I am not able to reply, hence a followup)
In article <1211 at ttds.UUCP> jonasn at 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 at cwi.nl
BITNET/EARN: dik at mcvax
>From dik at 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 at boring.cwi.nl (Dik T. Winter)
Message-Id: <8906062326.AA01677 at boring.cwi.nl>
To: draken!ttds!jonasn at kth.uucp
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211 at ttds.UUCP>
References: <1207 at ttds.UUCP>
Organization: CWI, Amsterdam
In article <1211 at 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 at cwi.nl
BITNET/EARN: dik at mcvax
To: jonasn at ttds.UUCP
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211 at ttds.UUCP>
References: <1207 at ttds.UUCP>
Organization: CWI, Amsterdam
In article <1211 at 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 at cwi.nl
BITNET/EARN: dik at mcvax
To: mcvax!kth!draken!ttds!jonasn
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211 at ttds.UUCP>
References: <1207 at ttds.UUCP>
Organization: CWI, Amsterdam
In article <1211 at 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 at cwi.nl
BITNET/EARN: dik at mcvax
To: jonasn at ttds.UUCP
Subject: Re: DS3100: buggy cc
Newsgroups: comp.unix.ultrix
In-Reply-To: <1211 at ttds.UUCP>
References: <1207 at ttds.UUCP>
Organization: CWI, Amsterdam
In article <1211 at 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 at cwi.nl
BITNET/EARN: dik at mcvax
More information about the Comp.unix.ultrix
mailing list