On 5/21/06, Thomas Dickey <[EMAIL PROTECTED]> wrote:
On Sun, May 21, 2006 at 05:09:32PM -0400, Albert Cahalan wrote:
>
> End result: it acts like bzero() when src==dst
hmm - someone should fix that broken implementation of memcpy.
It's damn fast. I like fast libraries, do
On 5/21/06, Thomas Dickey <[EMAIL PROTECTED]> wrote:
On Sun, May 21, 2006 at 09:20:17AM +0200, Albert Cahalan wrote:
> That is indeed a serious error.
no - it's a stupid but benign error:
source and destination addresses are the same
Consider this entirely reasonable
Package: xterm
Version: 210-3
Severity: normal
It's coming up as black-on-white now.
I realize that this is all sophisticated-looking, and I realize
that that are arcane ways to configure this, but...
We have gnome-terminal for people who don't care about
compatibility with the real thing and p
That is indeed a serious error.
Besides going either direction, memcpy doesn't need to work via bytes.
It could use 16-byte vector registers. It could use something like
PowerPC's dcbz instruction, which causes a cache line (of the
destination) to be allocated in an all-zero state rather than fet
On Sat, 2005-07-30 at 16:31 -0400, David Nusinow wrote:
> reassign 320627 xserver-xorg
> thanks
>
> On Sat, Jul 30, 2005 at 02:10:55PM -0400, Albert Cahalan wrote:
> > At least two people have managed to crash X by
> > trying to read the Florida law using xpdf.
>
>
Subject: crash w/ Florida law
Package: xserver-common
Version: multiple
At least two people have managed to crash X by
trying to read the Florida law using xpdf.
-- instructions for trying it --
Here is the Florida Administrative Code:
http://fac.dos.state.fl.us/faconline/chapter
I just spotted an error in the X FAQ. I've quoted it below,
as I saw it in a change log.
Sorry, but procps does not currently report IO memory as
part of the memory being used by the X server. The X server
is guilty as charged. Mine grows to about 300 MB on a system
with only 16 MB of RAM. Of cour
7 matches
Mail list logo
