Your message dated Mon, 02 Feb 2004 14:34:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#138080: Fixed?
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; 12 Mar 2002 23:57:23 +0000
>From [EMAIL PROTECTED] Tue Mar 12 17:57:23 2002
Return-path: <[EMAIL PROTECTED]>
Received: from shodan.irccrew.org [80.83.4.2] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16kw8w-0003wD-00; Tue, 12 Mar 2002 17:57:22 -0600
Received: by shodan.irccrew.org (Postfix, from userid 6976)
id 3AF284C09E; Wed, 13 Mar 2002 01:57:10 +0200 (EET)
Date: Wed, 13 Mar 2002 01:57:10 +0200
From: Timo Sirainen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: glibc regexps broken?
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
Package: libc6
Version: 2.2.5-3
I noticed this problem first time around 19. February with sid. Irssi's
regexp ignores/hilights crashes sometimes - not always and not reproducable,
sometimes it crashes every time doing regexp match and sometimes it can go
long time before crashing. I assume this is glibc bug because I've seen this
same backtrace many times now, and it has always been from Debian users.
Here's an example with ignoring "(away|gone|busy|back|return)"
#0 0x401c39f1 in kill () from /lib/libc.so.6
(gdb) bt
#0 0x401c39f1 in kill () from /lib/libc.so.6
#1 0x401c36d4 in raise () from /lib/libc.so.6
#2 0x401c4e51 in abort () from /lib/libc.so.6
#3 0x4024d47b in fnmatch () from /lib/libc.so.6
#4 0x4024a3e0 in fnmatch () from /lib/libc.so.6
#5 0x40253b0b in re_search_2 () from /lib/libc.so.6
#6 0x40253a93 in re_search () from /lib/libc.so.6
#7 0x40254093 in regexec () from /lib/libc.so.6
#8 0x080a99ea in ignore_match_pattern (rec=0x80f8928, text=0x83cc510 "utters
+the words, \"noi ot spo evig\"") at ignore.c:90
..
The regexp code is:
regcomp(&rec->preg, rec->pattern, REG_EXTENDED|REG_ICASE|REG_NOSUB);
..
regexec(&rec->preg, text, 0, NULL, 0);
---------------------------------------
Received: (at 138080-done) by bugs.debian.org; 2 Feb 2004 12:34:16 +0000
>From [EMAIL PROTECTED] Mon Feb 02 04:34:16 2004
Return-path: <[EMAIL PROTECTED]>
Received: from ip213-185-36-189.laajakaista.mtv3.fi (oma.irssi.org) [213.185.36.189]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AndHM-0007PO-00; Mon, 02 Feb 2004 04:34:16 -0800
Received: from localhost.kpnqwest.fi (localhost [127.0.0.1])
by oma.irssi.org (Postfix) with ESMTP id 5C33F3001891F
for <[EMAIL PROTECTED]>; Mon, 2 Feb 2004 14:34:14 +0200 (EET)
Subject: Re: Bug#138080: Fixed?
From: Timo Sirainen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
boundary="=-iGSYw1PX9gtNSN/XQUt9"
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5
Date: Mon, 02 Feb 2004 14:34:14 +0200
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_NUMBER autolearn=no
version=2.60-bugs.debian.org_2004_02_01
X-Spam-Level:
--=-iGSYw1PX9gtNSN/XQUt9
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Mon, 2004-02-02 at 13:45, Thomas Hood wrote:
> Do you still see this bug? There is some reason to think
> that it might have been fixed.
>=20
> If you no longer see the bug, please reply to
> [EMAIL PROTECTED] to close the report.
Couldn't reproduce it with a bit of testing, hopefully fixed :)
--=-iGSYw1PX9gtNSN/XQUt9
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBAHkPFyUhSUUBViskRAif1AJ95DtQjrXUuxgDavgp/sPvtUu1/TgCfQgxO
hNn+T6DdMQk71KCIlsA2Zm0=
=ak7D
-----END PGP SIGNATURE-----
--=-iGSYw1PX9gtNSN/XQUt9--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
