Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1513 - CVS seg.faults when CVS_RSH not set

Attached to Project: Arch Linux
Opened by Tommi Rantala (ttrantal) - Friday, 24 September 2004, 07:53 GMT
Last edited by Judd Vinet (judd) - Friday, 24 September 2004, 16:54 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

CVS 1.11.17 gives me segmentation faults when CVS_RSH is not set and the repository is to be accessed over ssh.

The problem seems to be caused by the patch 'rsh-args.diff' applied in the PKGBUILD.


Arch binary:
============

$ cat CVS/Root
:ext:username@host:/path/to/cvsroot
$ cvs add signal/
Segmentation fault
$ cvs update
Segmentation fault
$ gdb cvs
GNU gdb 6.2.1

(gdb) set args up
(gdb) r
Starting program: /usr/bin/cvs up
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x410c23c5 in strtok () from /lib/libc.so.6


Own binary without the patch:
=============================

$ cvs up
cvs [update aborted]: cannot exec rsh: No such file or directory
cvs [update aborted]: received broken pipe signal
$ export CVS_RSH="ssh"
$ cvs up
The authenticity of host '...' can't be established.
RSA key fingerprint is ..:..:......
Are you sure you want to continue connecting (yes/no)? yes
[...]

This task depends upon

Closed by  dorphell (dorphell)
Wednesday, 23 March 2005, 01:20 GMT
Reason for closing:  Not a bug
Additional comments about closing:  No bug here ;-)
Comment by dorphell (dorphell) - Friday, 24 September 2004, 20:59 GMT
Hum, didn't catch that while testing. Will remove the bugger I guess
Comment by Mike B (tehdely) - Sunday, 26 September 2004, 03:30 GMT
Christ, this is my fault. I'm sorry.
Comment by Judd Vinet (judd) - Tuesday, 22 March 2005, 18:50 GMT
Re-opened by request from Georg Grabler.
Comment by dorphell (dorphell) - Tuesday, 22 March 2005, 19:22 GMT
Gerog.. care to comment? I don't see what's the problem here.. the patch was removed..
Comment by Jan de Groot (JGC) - Tuesday, 22 March 2005, 22:19 GMT
I usually forget to set this var when doing package maintenance, and I never got any segfaults. Is the system that has these segfaults up2date?
Comment by Georg Grabler (STiAT) - Tuesday, 22 March 2005, 23:28 GMT
Well, i dont.

I've got this segfault, and it's gone since i set the var in my .bashrc.

I dont know when exactly it started crashing, but i think it has been working before i updated to kde 3.4.0, i'm not sure about this, since i've been two weeks off work, and didn't test it. Possible that there has been a CVS release in this time as well.

All i can tell you is that cvs definitely keeps crashing for me, with exactly the behaviour described here. That's why i requested the "re-opening" of this bug.

Kind regards,
GG
Comment by Georg Grabler (STiAT) - Tuesday, 22 March 2005, 23:29 GMT
Oh, what i forgot about: the system is 100% up to date.
Comment by dorphell (dorphell) - Tuesday, 22 March 2005, 23:55 GMT
But this bug was reproducible when I attended it months ago, now it's not, it's something more specific to your system setup.
Comment by Georg Grabler (STiAT) - Wednesday, 23 March 2005, 00:29 GMT
Well, i fixed it without changing anything on cvs, seems as if something was wrong, so ati-drivers were blocking the kernel update and all other updates as well. I've put in ati-drivers about ... 2 weeks ago, so it has been something specific about 2 weeks ago.

I've done a system upgrade now, and decided not to use any tur anymore, since they don't keep their repos on track.

I'm sorry for my mistake, and apologize for any inconvenience.

GG

Loading...