Your message dated Thu, 15 Dec 2005 09:08:08 +0000
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 0.8.10
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Mar 2003 23:32:53 +0000
>From [EMAIL PROTECTED] Wed Mar 26 17:32:52 2003
Return-path: <[EMAIL PROTECTED]>
Received: from e-64-35-146-236.empnet.net (green.zorcat.com) [64.35.146.236] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 18yKO4-0003Uu-00; Wed, 26 Mar 2003 17:32:52 -0600
Received: by green.zorcat.com (Postfix, from userid 1001)
        id C8AB9138C0; Wed, 26 Mar 2003 15:32:47 -0800 (PST)
Date: Wed, 26 Mar 2003 15:32:47 -0800
From: Nick Rusnov <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: For a good time, /eval $L
Message-ID: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Face: "Jm;fB-$7:=W"6S4Duu+&&[EMAIL 
PROTECTED]>fKyd,9K)]L6]Tz-{j3%;a.M,yZj[#ptI 
+kfBFL4f}qZ#-1dT..xT^D=vSFl,#Jzpp884`VyUP;Xh8aCt!f./7^G+yc~l_#V9\&_[gm*M|q=:ri 
+D=P"Km-j,$3nM0:63&bT-hNvy1JvcdL}zjz`!T7|e(~cfRy8Zc<oMx9X<j%^?0mXkCh/[pt/bR5zZ 
bO5rS\T&(fN20&/1PiWE*t1Ym}'[j+CK("ziHH26M>+/dTY0j1Isr3<*f^*o=*?Ehm5
X-GPG-Fingerprint: C461 6C25 33DA BA99 2A1F  0F3C 54D4 094C F121 9B84
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-2.2 required=4.0
        tests=HAS_PACKAGE,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,
              USER_AGENT,USER_AGENT_MUTT
        version=2.44
X-Spam-Level: 


Package: irssi-text
Version: 0.8.6-4

I noticed an interesting occurance when thinking about writing a
script for irssi. If you eval $L, instant segfault. If you eval
$L='something', irssi freezes and steadily consumes resources (on an
older system, this caused a total system failure; in my tests I was
able to kill the process before it crashed my other system). It seems 
reasonable that this is something you aught not to do, but it was so 
trivial to crash a system with, that I figured someone might want to 
know about it.

-- 
-><- Nick Rusnov
-><- http://nick.industrialmeats.com
-><- [EMAIL PROTECTED]/[EMAIL PROTECTED] 

---------------------------------------
Received: (at 186416-done) by bugs.debian.org; 15 Dec 2005 09:08:10 +0000
>From [EMAIL PROTECTED] Thu Dec 15 01:08:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from light.bluelinux.co.uk ([193.201.200.221] ident=postfix)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1Emp5t-0001gZ-Rt
        for [EMAIL PROTECTED]; Thu, 15 Dec 2005 01:08:10 -0800
Received: from light.bluelinux.co.uk (localhost [127.0.0.1])
        by light.bluelinux.co.uk (Postfix) with ESMTP id E044EE4479F
        for <[EMAIL PROTECTED]>; Thu, 15 Dec 2005 09:08:08 +0000 (GMT)
Received: by light.bluelinux.co.uk (Postfix, from userid 2042)
        id D1227E5B327; Thu, 15 Dec 2005 09:08:08 +0000 (GMT)
Date: Thu, 15 Dec 2005 09:08:08 +0000
From: David Pashley <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: fixed in 0.8.10
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
X-AV-Checked: ClamAV using ClamSMTP
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02

This is fixed in 0.8.10, so closing.

-- 
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua stulta superstitione.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to