, and I suspect this is moderately widespread;
I've seen it on recent Ubuntu, recent RaspOS, and old NetBSD. I wrote
a tiny test (ftp.rodents-montreal.org:/mouse/misc/cursor-bug.c - also
available over HTTP as well, though I'm not sure what Content-Type:
it'll be served as) and people on NetBSD's tech
>> [...bug in some CreateCursor implementations...]
>> [test case ftp.rodents-montreal.org:/mouse/misc/cursor-bug.c]
>> I wrote patches to fix this for two server versions
(fairly old server versions, by now)
>> (though I do have low-to-negative confidence I got the
program for them available from
ftp.rodents-montreal.org, in /mouse/X/cursorbug.c; it has an extensive
comment header explaining what the bugs in question are, and the code
is deliberately minimalist, intended to be easy to understand.
I wrote to NetBSD's tech-x11 list about this; someone
Operating System: NetBSD DP-Frank.Rodents-Montreal.ORG 5.2 NetBSD 5.2
(DP) #0: Tue May 14 03:28:46 EDT 2013
mo...@dp.rodents-montreal.org:/home/mouse/kbuild/DP amd64
Build Date: 09 July 2009 12:14:03AM
I know at least some of that is false; I've done a build-and-reinstall
of the world
there are also
portability reasons to not depend on nonzero values of the argument
doing anything meaningful (possibly excepting -100 and 100, to which
the above remarks apply).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
not clear it really makes any
pragmatic difference. Now, at least.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
like the syntax, because it looks as though it is going to have
horrible parsing ambiguities in the presence of comma operators or
multiple variable declarations in the init portion.)
I should ask my go-to guy for C questions about this.
/~\ The ASCII Mouse
\ / Ribbon
to decide whether you consider that a plausible SE case.)
It was originally done that way to make it easier for Fortran
compilers, AFAIK.
A C feature was done to make it easier for FORTRAN compilers? I'm not
sure what that could even _mean_.
/~\ The ASCII Mouse
that
impossible? (Seems dubious to me, especially given the existence of
PCI-to-ISA bridges - but I don't know peecee video hardware very well.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7
far as to say that adding FamilyLocal, or,
worse, replacing it with FamilyLocal, is a bug.
Though, as always, that opinion is probably worth what you paid for it.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
and/or ::1, or for names that resolve to one/both of those
but also at least one other address.)
I can repost the patches here, but [...]
No, not relevant; it's the behaviour I'm talking about, not the
implementation of it.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against
makes the porting effort a lot
higher in such cases.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
work with).
The above guess is based on core X keyboard mapping, for which the
first four KeySyms have reasonably well-defined interpretation.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61
conceptually wrong, even though
if (as seems likely) False is #defined to 0 it's actually valid C.
Should this maybe be 0 instead of False?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7
(http://ftp.rodents-montreal.org/mouse/blah/2009-10-09-1.html) for why.
I do, however, agree that NULL, for all its problems, is better than
False in this usage. :-)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
for open-source
work no matter _what_ it actually turns out to permit.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
, but my stance
on this would be don't do that, then. PID 1 is init is so
ingrained in the UNIX way that I would even go so far as to call it a
bug for Linux to be handing out PID 1 to anything but init under any
circumstances.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
#define CMSPACE(x) (sizeof(struct cmsghdr)+(x))
#define CMLEN(x) (sizeof(struct cmsghdr)+(x))
#define CMSKIP(x) (sizeof(struct cmsghdr))
#endif
#endif
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
; there probably exist
uses for mutex-free condvars, and this may be one of them)
In any case, the mutex does not have to actually cause any trouble, if
present; it can be acquired and released immediately around the condvar
calls.
/~\ The ASCII Mouse
\ / Ribbon
hardware outweighed the win
of scheduling an unusual timer internval.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org
break the
server - and wasn't this concern about a client-side thing? I'm not
entirely sure how all these parts fit together, but that was the
impression I got. Was that impression wrong?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
is
(still) broken like that.
Perhaps fortunately for X, it's easy to test for if you don't mind
building and running a test program - which, since X seems to have now
drunk the autoconf koolaid :(, I infer is not a problem.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
___
xorg-devel@lists.x.org: X.Org development
Archives: http
a lot more than file descriptors - and I've wished for it often
enough before; it would hardly be specific to this application.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39
approach at least abstracts away the knowledge
about where to put the files;
I'm not convinced that's a good thing, because it also removes control
over where to put the files (when there are files).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
, something is wrong anyway (from my understanding).
After all this is the trigger of the bug.
Does anyone know whether the bug triggers on systems with 64-bit longs?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email
bits aren't all the same, but they can be fixed with
a little more code.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
the price. In something
as big as X, the conversion would admittedly be a big job, but I would
most definitely recommend doing it (though I realize that is armchair
quarterbacking).
I think the only thing I use a qualifier-stripper for is writev().
/~\ The ASCII Mouse
Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info
really pointers
to someone reading the code, which they'd better not be if they're
being kept in 32-bit ints on 64-bit-pointer architectures.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D
[...the security extension...] A lot of people use X remotely with
ssh which is unsafe without something like this.
What's unsafe about that? I don't see anything offhand, but I haven't
thought about it for long enough for that to mean much.
/~\ The ASCII Mouse
Ideally, we'll eventually write code which makes all core operations
faster with the GPU than with the CPU.
What if there is no GPU? Will support for such systems be dropped?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
that's the same when it's on stdout of course (well, worse, since you
can't filter at all).
Can't? Is there anything x.org runs on that doesn't support something
greppish?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents
had its weaknesses, but it ran on a _lot_ of hardware and
software pairings.
Is X.org dropping - has X.org dropped - that? Sure sounds like it.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8
Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info
36 matches
Mail list logo
