Bug 5067 – gftp crashes without warning

Bug 5067 - gftp crashes without warning

Summary:	gftp crashes without warning

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	gftp (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Mason
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-09-11 06:42 EDT by margarita
Modified:	2008-05-01 11:37 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-03 12:02:37 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description margarita 1999-09-11 06:42:56 EDT

gftp crashes after several downloads were made from
Red Hat's site. The crashes were abrupt, without warning
and occurred just after the download selection was made.

There was no core file and /var/log/messages reveals no
clues as to the cause of the crash.

Intel i586 kernel
64 meg 60ns EDO ram
Iwill primium motherboard
Adaptec and IBM SSCI drive 9.1 GIG
Mellinium card with 2 meg and Viewsonic P810

Comment 1 David Lawrence 1999-09-14 11:30:59 EDT

I was not able to get this to fail using the latest gftp package
available from
ftp://ftp.redhat.com/redhat/updates/6.0/i386/gftp-2.0.3-1.i386.rpm.

Comment 2 margarita 1999-09-18 15:06:59 EDT

I did contact the author because his name and e-mail was on the
application. He was able to recreate the crash. He is going to fix it
on the next release. I realise that it was a difficult crash to
duplicate beacuse it took quite a while using it for it to happen. I
am writing to make the record complete.

Comment 3 Elliot Lee 2000-02-03 12:02:59 EST

Reporter indicates the bug will be fixed in next upstream release.

Note You need to log in before you can comment on or make changes to this bug.