54172 – nget 0.26 segfaults

Bug 54172 - nget 0.26 segfaults

Summary: nget 0.26 segfaults

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Ryan Phillips (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-06-17 00:13 UTC by Lasse Kärkkäinen
Modified:	2005-02-06 18:38 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

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

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

Description Lasse Kärkkäinen 2004-06-17 00:13:00 UTC

I got some repeatable segfaults with Gentoo build of nget, but after manually rebuilding from the source tarball, with --enable-debug, I no longer get those.

The sigsegv was caused by a read of 4 bytes from address 0x148 (or so). This usually means reference by p[0x148], where p is a null pointer. It happened inside nget itself, but I didn't have debug enabled, so I don't know in more detail.

The bug may be related to handling big files.

For the record: the machine this was tested on is rock-solid and doesn't have any memory faults or anything. It has been in production use with 60 days of uptime now (running 2.6.4-cko4).

Comment 1 Starz McCllelan 2004-06-18 22:19:01 UTC

I have also gotten segs with nget 0.26, I usually just clear the cache and it ends up not being an issue any longer. I don't know, but maybe #54387 will help/fix.

Comment 2 Ryan Phillips (RETIRED) gentoo-dev

2005-02-06 18:38:07 UTC

0.27 in cvs.  did it fix the problem?