All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Kawa <jfk@zeus.polsl.gliwice.pl>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Register corruption --patch
Date: Wed, 20 Oct 2004 02:34:08 +0200	[thread overview]
Message-ID: <20041020003408.GA6101@finwe.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0410191112100.4820@chaos.analogic.com>

Richard B. Johnson wrote:

> This 'C' compiler destroys parameters passed to functions
> even though the code does not alter that parameter.
[example]
> This was from /usr/src/linux-2.6.9/arch/i386/kernel/semaphore.c
> It this case, the value of 'sem' is destroyed which means that
> certain assembly-language helper functions no longer work.
> 
> This was discovered by Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>
> 
> I have been having trouble with mysterious things like:
[...]
> (4) Data errors in email.
> (5) Network connections failing to go away `netstat -c` shows
> hundreds of lines of very old history.
> ... etc.
> 

Having troubles with some strange (and -as it seems- temporary) 
data corruptions here[*], I was wondering, whether would it be 
posiible to easily diagnose this somehow?

[*] like diff running serval times over same two files can 
    only once in a while show one character altered 

bye

-- 
Jacek Kawa  **Define the universe.  Give three examples.** [r.h.f.r]

  reply	other threads:[~2004-10-20  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 15:14 Register corruption --patch Richard B. Johnson
2004-10-20  0:34 ` Jacek Kawa [this message]
2004-10-20 12:44   ` Richard B. Johnson
2004-10-20 20:27     ` Jacek Kawa
2004-10-20 20:37       ` Richard B. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041020003408.GA6101@finwe.eu.org \
    --to=jfk@zeus.polsl.gliwice.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.