mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Ortwin Glück" <odi@odi.ch>, linux-kernel@vger.kernel.org
Subject: Re: freeze when strace X
Date: Wed, 9 Jun 2010 22:47:23 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1006092232180.2933@localhost.localdomain> (raw)
In-Reply-To: <20100609200610.GA27536@srcf.ucam.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 923 bytes --]

On Wed, 9 Jun 2010, Matthew Garrett wrote:

> On Wed, Jun 09, 2010 at 10:02:21PM +0200, Ortwin Glück wrote:
> > On 09.06.2010 21:52, Matthew Garrett wrote:
> > > Just to make sure, you're not trying to strace X from within X, are you?
> > 
> > Oh... now that you mention it... Is that a silly thing to do?
> > strace X from a different terminal works fine :-)
> > 
> > But freezing the system because of that? I mean an error message, log, anything
> > would be "nice".
> 
> strace needs to output text via X, which generates output which needs to 
> be output via X... and you'll tend to deadlock. If X is holding any 
> interesting kernel locks at that point then it wouldn't surprise me if 
> the machine ends up dead.

Nothing to do with kernel locks. strace hooks into the syscall and
intercepts the data, so X is stopped at that point. Now try to send
output to a program which you stopped yourself :)

Thanks,

	tglx

  parent reply	other threads:[~2010-06-09 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 18:38 Ortwin Glück
2010-06-09 19:52 ` Matthew Garrett
2010-06-09 20:02   ` Ortwin Glück
2010-06-09 20:06     ` Matthew Garrett
2010-06-09 20:26       ` Ortwin Glück
2010-06-09 20:47       ` Thomas Gleixner [this message]
2010-06-09 20:53         ` Matthew Garrett

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=alpine.LFD.2.00.1006092232180.2933@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=odi@odi.ch \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®