From smkelly@zombie.org  Tue Oct 31 10:21:53 2000
Return-Path: <smkelly@zombie.org>
Received: from area51.slashnet.org (area51.slashnet.org [208.222.214.95])
	by hub.freebsd.org (Postfix) with ESMTP id 2684937B4CF
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 31 Oct 2000 10:21:53 -0800 (PST)
Received: from edgemaster.zombie.org (edgemaster.creighton.edu [147.134.107.69])
	by area51.slashnet.org (Postfix) with ESMTP id 0CD7B14D436
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 31 Oct 2000 13:21:52 -0500 (EST)
Received: by edgemaster.zombie.org (Postfix, from userid 1001)
	id AF25798A4; Tue, 31 Oct 2000 12:21:49 -0600 (CST)
Message-Id: <20001031182149.AF25798A4@edgemaster.zombie.org>
Date: Tue, 31 Oct 2000 12:21:49 -0600 (CST)
From: smkelly@zombie.org
Reply-To: smkelly@zombie.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: screen segfault
X-Send-Pr-Version: 3.2

>Number:         22444
>Category:       ports
>Synopsis:       The 'screen' port has reproducable segfaults
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    ache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 31 10:30:01 PST 2000
>Closed-Date:    Fri Sep 28 07:20:34 PDT 2001
>Last-Modified:  Fri Sep 28 07:20:51 PDT 2001
>Originator:     Sean Kelly
>Release:        FreeBSD 4.1.1-STABLE i386
>Organization:
>Environment:

screen-3.9.8_3

FreeBSD edgemaster.zombie.org 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Tue Oct 24 0
0:37:00 CDT 2000     smkelly@edgemaster.zombie.org:/usr/obj/usr/src/sys/EDGEMAST
ER  i386

>Description:

Under reproducable (though not well understood) and some unknonw conditions
screen will crash with signal 11.

>How-To-Repeat:

If I start the mutt MUA from within screen, screen will always segfault when
I open my mail folders.  I assume it has something to do with the appearance
of my screen at the time, but I am not sure.  I have also seen screen crash
due to the EPIC IRC client.  The actual condition it crashes under is unknown
to me.

Program received signal SIGHUP, Hangup.
0x2813ffb4 in sigsuspend () from /usr/lib/libc.so.4
(gdb) bt
#0  0x2813ffb4 in sigsuspend () from /usr/lib/libc.so.4
#1  0x2813f724 in sigpause () from /usr/lib/libc.so.4
#2  0x28135fb2 in pause () from /usr/lib/libc.so.4
#3  0x806c9d4 in free ()
#4  0x804ba49 in free ()
#5  0x8049f29 in free ()
(gdb)

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports->ache 
Responsible-Changed-By: sobomax 
Responsible-Changed-When: Fri Nov 3 06:42:23 PST 2000 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22444 

From: "David W. Chapman Jr." <dwcjr@inethouston.net>
To: <FreeBSD-gnats-submit@freebsd.org>, <smkelly@zombie.org>
Cc: <dwcjr@FreeBSD.org>
Subject: Re: ports/22444: The 'screen' port has reproducable segfaults
Date: Sat, 22 Sep 2001 19:33:37 -0500

 Does this problem still exist?
 
 

From: Sean Kelly <smkelly@zombie.org>
To: "David W. Chapman Jr." <dwcjr@inethouston.net>
Cc: FreeBSD-gnats-submit@freebsd.org, dwcjr@FreeBSD.org
Subject: Re: ports/22444: The 'screen' port has reproducable segfaults
Date: Fri, 28 Sep 2001 03:17:34 -0500

 On Sat, Sep 22, 2001 at 07:33:37PM -0500, David W. Chapman Jr. wrote:
 > Does this problem still exist?
 
 No.  It's been gone for a while.
State-Changed-From-To: open->closed 
State-Changed-By: dwcjr 
State-Changed-When: Fri Sep 28 07:20:34 PDT 2001 
State-Changed-Why:  
Problem has been gone for a while. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22444 
>Unformatted:
