Your message dated Thu, 29 Jan 2004 08:05:33 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Closing this bug
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; 2 Sep 2000 03:54:06 +0000
>From [EMAIL PROTECTED] Fri Sep 01 22:54:06 2000
Return-path: <[EMAIL PROTECTED]>
Received: from adsl-63-193-116-241.dsl.snfc21.pacbell.net (kitenet.net) 
[::ffff:63.193.116.241] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 13V4Na-00041O-00; Fri, 01 Sep 2000 22:54:06 -0500
Received: by kitenet.net (Postfix, from userid 500)
        id B7C5DBC049; Fri,  1 Sep 2000 20:54:05 -0700 (PDT)
From: Joey Hess <[EMAIL PROTECTED]>
Subject: textutils: tail segfault
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.4
Message-Id: <[EMAIL PROTECTED]>
Date: Fri,  1 Sep 2000 20:54:05 -0700 (PDT)
Delivered-To: [EMAIL PROTECTED]

Package: textutils
Version: 2.0-3
Severity: minor

Note severity. I don't think this happens in everyday use.

[EMAIL PROTECTED]:~>ulimit -a
cpu time (seconds)         unlimited
file size (blocks)         unlimited
data seg size (kbytes)     81920
stack size (kbytes)        8192
core file size (blocks)    0
resident set size (kbytes) 81920
processes                  150
file descriptors           1024
locked-in-memory size (kb) unlimited
virtual memory size (kb)   81920
[EMAIL PROTECTED]:~>tail /dev/zero
zsh: segmentation fault  tail /dev/zero

If I disable memory limits, it doesn't segfault. Of course, it eventually
eats up all memory on the machine and gets killed.

-- System Information
Debian Release: woody
Kernel Version: Linux kite 2.2.16 #1 Sun Jun 11 15:30:48 PDT 2000 i686 unknown

Versions of the packages textutils depends on:
ii  libc6          2.1.3-10       GNU C Library: Shared libraries and Timezone

---------------------------------------
Received: (at 70762-done) by bugs.debian.org; 29 Jan 2004 16:05:42 +0000
>From [EMAIL PROTECTED] Thu Jan 29 08:05:42 2004
Return-path: <[EMAIL PROTECTED]>
Received: from marge.v3.ca [216.66.20.89] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1AmEfm-0000O9-00; Thu, 29 Jan 2004 08:05:42 -0800
Received: from marge.v3.ca (localhost [127.0.0.1])
        by marge.v3.ca (8.12.11.Beta0/8.12.11.Beta0/Debian-1) with ESMTP id 
i0TG5XGu008516
        (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
        for <[EMAIL PROTECTED]>; Thu, 29 Jan 2004 08:05:33 -0800
Received: (from [EMAIL PROTECTED])
        by marge.v3.ca (8.12.11.Beta0/8.12.10/Debian-0) id i0TG5Xv0008515
        for [EMAIL PROTECTED]; Thu, 29 Jan 2004 08:05:33 -0800
X-Authentication-Warning: marge.v3.ca: jbailey set sender to [EMAIL PROTECTED] using -f
Date: Thu, 29 Jan 2004 08:05:33 -0800
From: Jeff Bailey <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Closing this bug
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-EMSscan-MailScanner: Found to be clean
X-EMSscan-MailScanner-SpamCheck: not spam, SpamAssassin (score=-9.009,
        required 5, BAYES_00 -4.90, USER_AGENT_MUTT -4.11)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_27 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no 
        version=2.60-bugs.debian.org_2004_01_27
X-Spam-Level: 

Several people (including me) have verified now that this bug is fixed. 
Closing it.

Tks,
Jeff Bailey


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

Reply via email to