All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D. Bahi" <dbahi@enterasys.com>
To: Nicholas Nethercote <njn25@cam.ac.uk>
Cc: Jeff Dike <jdike@addtoit.com>, Tom Hughes <thh@cyberscience.com>,
	user-mode-linux-devel@lists.sourceforge.net,
	valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Re: [uml-devel] Re: UML and valgrind
Date: Thu, 05 Aug 2004 09:15:32 -0400	[thread overview]
Message-ID: <411232F4.5030007@enterasys.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0408051026120.21344@hermes-1.csi.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

ok, great.

now where do i put this snippet - because it doesn't
belong in the file mentioned in the earliest post...
(or if it does - i don't see how). is there someone
willing to 'modernize' this patch for the clueless
user (me ;)

thanks very much.

Nicholas Nethercote wrote:

> On Wed, 4 Aug 2004, Jeff Dike wrote:
> 
>> It feels to me more like the valgrind thread runs a system call with no
>> perceptible effect, and there's this new thread all of a sudden which 
>> runs
>> happily in this address space because it can't tell that valgrind is 
>> there.
> 
> 
> To summarise:  you seem to be confident there won't be any problems, and 
> Tom's not so sure.  I'm not sure either, but the 
> threads/signals/syscalls stuff is the part of Valgrind I understand the 
> least.  I would say, just don't be shocked if you do this and weird 
> things start happening :)
> 
> N


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

  reply	other threads:[~2004-08-05 13:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08  4:13 [uml-devel] UML and valgrind Bahi, David
2004-08-03  2:47 ` [uml-devel] " D. Bahi
2004-08-03  5:17   ` Jeff Dike
2004-08-03  9:31     ` [Valgrind-users] " Nicholas Nethercote
2004-08-03 14:50       ` Jeff Dike
2004-08-03 14:31         ` Nicholas Nethercote
2004-08-03 17:50           ` Jeff Dike
2004-08-03 17:33             ` D. Bahi
2004-08-03 19:31               ` Jeff Dike
2004-08-03 20:12                 ` D. Bahi
2004-08-04  7:47                   ` Tom Hughes
2004-08-03 22:04                 ` Nicholas Nethercote
2004-08-04  7:52                 ` Tom Hughes
2004-08-04 15:10                   ` Jeff Dike
2004-08-04 15:35                   ` Jeff Dike
2004-08-04 14:58                     ` Tom Hughes
2004-08-04 18:00                       ` Jeff Dike
2004-08-04 17:57                         ` Tom Hughes
2004-08-04 21:02                           ` Jeff Dike
2004-08-05  9:28                             ` Nicholas Nethercote
2004-08-05 13:15                               ` D. Bahi [this message]
2004-08-05 15:24                               ` Jeff Dike
2004-08-03 19:40               ` Jeff Dike
2004-08-04  1:09               ` Nuno Silva
2004-08-04  2:47                 ` D. Bahi

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=411232F4.5030007@enterasys.com \
    --to=dbahi@enterasys.com \
    --cc=jdike@addtoit.com \
    --cc=njn25@cam.ac.uk \
    --cc=thh@cyberscience.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=valgrind-users@lists.sourceforge.net \
    /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.