From jsd@flaya.gamespot.com  Mon Mar 30 12:46:09 1998
Received: from flaya.gamespot.com (flaya.gamespot.com [206.169.18.26])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17582
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 30 Mar 1998 12:46:05 -0800 (PST)
          (envelope-from jsd@flaya.gamespot.com)
Received: (from jsd@localhost)
	by flaya.gamespot.com (8.8.8/8.8.8) id MAA01956;
	Mon, 30 Mar 1998 12:46:02 -0800 (PST)
	(envelope-from jsd)
Message-Id: <199803302046.MAA01956@flaya.gamespot.com>
Date: Mon, 30 Mar 1998 12:46:02 -0800 (PST)
From: jsd@gamespot.com
Reply-To: jsd@gamespot.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: running architextSearch (excite) under linux emu coredumps when exiting with error
X-Send-Pr-Version: 3.2

>Number:         6176
>Category:       bin
>Synopsis:       running architextSearch (excite) under linux emu coredumps when exiting with error
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 30 12:50:06 PST 1998
>Closed-Date:    Sat Mar 2 09:17:21 PST 2002
>Last-Modified:  Sat Mar 02 09:17:52 PST 2002
>Originator:     Jon Drukman
>Release:        FreeBSD 2.2.6-RELEASE i386
>Organization:
gamespot inc.
>Environment:
>Description:

Using Excite's free search engine (architext) under the linux
emulation system, whenever one of the binaries (architextIndex
or architextSearch) exits with an error, it also dumps core.
One possible error condition for the searcher is "term not found".
So, people are querying our search engine all day long and the
logs fill up with spurious "Segmentation violation" and
"architextSearch exited on signal 11" messages.  There is no
other impact other than an annoying extraneous message.

Oddly enough, i downloaded the BSDI package and it does the exact
same thing!  Succesful completion is ok, error exits dump core.

BTW, i apologize if this is in the wrong category.  I'm not sure
if the linux emulator is kernel or ports...
>How-To-Repeat:

Download the excite package from ftp.excite.com:/ews/1.1p1/linux
and try it out.

>Fix:
	
i don't know enough about the linux emulator to fix it.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-> 
Responsible-Changed-By: obrien 
Responsible-Changed-When: Tue Jul 28 11:16:55 PDT 1998 
Responsible-Changed-Why:  
This is a "bin" issue, not ports issue. (I believe) 
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Sun Dec 2 09:57:20 PST 2001 
State-Changed-Why:  

Does this still occur with more recent FreeBSD releases? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6176 
State-Changed-From-To: feedback->closed 
State-Changed-By: iedowse 
State-Changed-When: Sat Mar 2 09:17:21 PST 2002 
State-Changed-Why:  

Feedback timeout. 

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