All of lore.kernel.org
 help / color / mirror / Atom feed
From: davidw@dedasys.com (David N. Welton)
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org, Greg Weeks <greg.weeks@timesys.com>
Subject: Re: threaded core dump oops
Date: 24 Mar 2004 13:25:55 +0100	[thread overview]
Message-ID: <87y8pqa0to.fsf@dedasys.com> (raw)
In-Reply-To: 20040323212448.GD2330@smtp.west.cox.net


Tom Rini <trini@kernel.crashing.org> writes:

> > [ Please CC replies to me - thanks! ]

> > Hi,

> > Looking around, after bumping into this bug myself I found this:

> > http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/0566.html

> > and was wondering if it will be going in anytime soon.  If not, is
> > there anything I can do to help?  I can reproduce the Oops
> > reliably...

> Probably in time for 2.6.6-rc1 (I'm trying to take the term "release
> candidate" seriously, at least for what I'm passing along).  A
> simple program which causes the oops would be quite helpful, too.

Well, it's not as simple as a small C program, but this will do the
job on Debian testing (*):

echo "package require Expect" | tclsh8.4

The problem is that Tcl 8.4 is threaded, Expect isn't, and something
goes wrong when Expect gets loaded into Tcl.

--
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/

(*) If no one uploads an updated Expect package anytime soon, the bad
    version is: 5.39.0-1

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2004-03-24 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 13:47 threaded core dump oops David N. Welton
2004-03-23 21:24 ` Tom Rini
2004-03-24 12:25   ` David N. Welton [this message]

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=87y8pqa0to.fsf@dedasys.com \
    --to=davidw@dedasys.com \
    --cc=greg.weeks@timesys.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    /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.