ports/74177: misc/linux-edonkey-tool-recovermet problem (maybe linux_compat/kern bug)

No Name arundel at h3c.de
Sat Nov 20 23:10:33 UTC 2004

>Number:         74177
>Category:       ports
>Synopsis:       misc/linux-edonkey-tool-recovermet problem (maybe linux_compat/kern bug)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 20 23:10:32 GMT 2004
>Originator:     No Name
>Release:        FreeBSD 5.3-RELEASE i386
System: FreeBSD skatecity 5.3-RELEASE FreeBSD 5.3-RELEASE #3: Mon Nov 8 01:54:22 CET 2004 arundel at skatecity:/usr/obj/usr/src/sys/ARUNDEL i386

	While running misc/linux-edonkey-tool-recovermet over this file:

	-rw-r--r--  1 arundel  arundel  -      2149888206 Nov 20 23:29 1.part

	I got the following error message:

	File: Temp/1.part
	Size: -2145079090 bytes <-- Uhuh :( !!!!!
	Partial hashes: 222


	fseek () error. Couldn't reach block

	Block 221: 00000000000000000000000000000000  -  100% done

	Digesting known.met and all x.part.met...
	228 known files in known.met and x.part.met. Retrieving info...
	Segmentation fault (core dumped)

	The problem seems to be some kind of limitation (buffer, variable) or
	a faulty cast or conversion (80b -> 64b). Could somebody check, if this
	is a bug in the software, in which case there is not much to do, because
	the file is linux-closed-source. Or if this is a bug in the the linux compat
	layer or somewhere ine the base system.

	I don't think there are any 2gb file limitations left in BSD, but who

	Install the app und use it on a big file (> 2gb).




More information about the freebsd-ports-bugs mailing list