When trying to run cvsup on 5.3 (installed from official ISOs) on an amd64 trough a socks server we get the following error: ================== xenon# runsocks cvsup -P m -L 1 /usr/share/examples/cvsup/ports-supfile -h cvsup1.ro.freebsd.org @M3novm Connected to cvsup1.ro.freebsd.org *** *** runtime error: *** Subscript out of range *** file "/u2/ports/net/cvsup-without-gui/work/cvsup-snap-16.1h/suplib/src/SupMisc.m3", line 216 *** use option @M3stackdump to get a stack trace Abort (core dumped) ================== here is with the stack dump ================== xenon# runsocks cvsup -P m -L 1 /usr/share/examples/cvsup/ports-supfile -h cvsup1.ro.freebsd.org @M3novm @M3stackdump Connected to cvsup1.ro.freebsd.org *** *** runtime error: *** Subscript out of range *** file "/u2/ports/net/cvsup-without-gui/work/cvsup-snap-16.1h/suplib/src/SupMisc.m3", line 216 *** ------------------ EXCEPTION HANDLER STACK --------------------- 0x7fffffffc410 TRY-FINALLY proc = 0x44f18f frame = 0x7fffffffc460 0x7fffffffc510 TRY-EXCEPT {CVProto.NotSupported, TokScan.Error} 0x7fffffffcb50 TRY-FINALLY proc = 0x41cd8d frame = 0x7fffffffd3e0 0x7fffffffcb70 TRY-FINALLY proc = 0x41cdb6 frame = 0x7fffffffd3e0 0x7fffffffcb90 TRY-FINALLY proc = 0x41cdd4 frame = 0x7fffffffd3e0 0x7fffffffce30 TRY-FINALLY proc = 0x41cebf frame = 0x7fffffffd3e0 0x7fffffffd0e0 TRY-EXCEPT {Wr.Failure, FSClient.TransientFailure, Thread.Alerted, Rd.Failure, Rd.EndOfFile, FSClient.Error} 0x7fffffffd750 TRY-FINALLY proc = 0x4251af frame = 0x7fffffffe950 0x7fffffffda00 TRY-EXCEPT {Main.Error} 0x7fffffffdf10 TRY-EXCEPT {Thread.Alerted} ---------------------------------------------------------------- Abort (core dumped) ================= The socks does work ok with other applications (tested with "runsocks ftp something" and "runsocks telnet somewhere") even "runsocks cvsup /usr/share/examples/cvsup/ports-supfile -h cvsup.freebsd.org" (with no other flags) will give the same error. Unfortunatelly I cannot test in an non-socks environement. Thank you very much. How-To-Repeat: runsocks cvsup -P m /usr/share/examples/cvsup/ports-supfile your.cvs.server @M3novm
Responsible Changed From-To: freebsd-ports-bugs->jdp jdp@ of cvsup/ezm3-fame might want to look at this.
Hi, A similar error occurs on an amd64 with the following command: cvsup -g -l /tmp/cvsup.lck -L 2 /etc/cvsup/ports-supfile This is the error: *** *** runtime error: *** Value out of range *** file "/u2/ports/lang/ezm3/work/ezm3-1.1/libs/libm3/src/os/POSIX/FilePosix.m3", line 171 *** Abort trap (core dumped) And this is the stack trace: ------------------ EXCEPTION HANDLER STACK --------------------- 0x7fffffffd360 TRY-EXCEPT {OSError.E} 0x7fffffffd600 TRY-FINALLY proc = 0x438d74 frame = 0x7fffffffd660 0x7fffffffda00 TRY-EXCEPT {OSError.E} 0x7fffffffdc80 TRY-EXCEPT {Main.Error} 0x7fffffffe190 TRY-EXCEPT {Thread.Alerted} ---------------------------------------------------------------- Best regards, Martijn
Responsible Changed From-To: jdp->amd64 Thanks for the report, but I have no idea how to fix this and I don't have an amd64 system to attempt it. The amd64 support for CVSup is very spotty; it's a miracle it works at all. I'm reassigning this bug to amd64@freebsd.org.
Responsible Changed From-To: amd64->freebsd-amd64 fix assigned to
Responsible Changed From-To: freebsd-amd64->bzeeb+freebsdports@zabbadoz.net See if Bjoern could possibly be interested in fixing this.
State Changed From-To: open->feedback Does that problem still exists with todays cvsup on amd64? The time the PR was filed we only ditributed binaries but not the possibility to build from source. Could you please check and let me know.
Responsible Changed From-To: bzeeb+freebsdports@zabbadoz.net->bz use bz@ and not my private address for ports tracking.
State Changed From-To: feedback->open ru@ confirmed that the problem still exists. I'll see if I can find the problem (amd64 is no officially supported platform). Maybe using lockf(1) as a workaround for the -l problem might help in the meantime.
State Changed From-To: open->closed A patch was committed by ru@, see: http://docs.freebsd.org/cgi/mid.cgi?200604171348.k3HDmBBM005096 Thanks for reporting.
State Changed From-To: closed->open re-open. Sorry I had missed the socks issue while closing.
Is the socks problem still an issue for you now that there is csup for client mode? If so, how can I build a setup to reproduce it? If no - may I close the PR?
State Changed From-To: open->closed Submitters email bounces and it wasn't an issue for anyone else. If you do not need mirror mode with a socks proxy on the not-officially supported am64 version, use csup.