Date: Sat, 13 Dec 2008 18:31:21 -0800 From: "Garrett Cooper" <yanefbsd@gmail.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: SIGPIPE with CVS and CURRENT? Message-ID: <7d6fde3d0812131831ucc9cd71scabbfa045192242e@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi guys,
I just came across this issue trying to update a repository to
push some patches upstream to another project I work with:
[gcooper@optimus /scratch/ltp]$ gdb cvs
Type "help" followed by command name for full documentation.
Command name abbreviations are allowed if unambiguous.
(gdb) set args up
(gdb) r
Starting program: /usr/bin/cvs up
Program received signal SIGPIPE, Broken pipe.
0x0000000800bdfeec in write () from /lib/libc.so.7
[gcooper@optimus /scratch/ltp]$ uname -a
FreeBSD optimus.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #9:
Sun Dec 7 17:44:13 PST 2008
gcooper@optimus.gateway.2wire.net:/usr/obj/usr/src/sys/OPTIMUS amd64
It looks like a corrupted stack of some flavor because when I do
bt it prints out hundreds of ??? before it eventually fails.
The sources I originally saw this issue with were based off mid
November (don't know when to look up the actual version date because
I've rebuilt the kernel a few times and cvsup'ed once or twice since
then), but my previous major sync (mid October 2008) didn't yield this
issue. I just recently rebuilt kernel + world (today) and I'm getting
the same result.
Other apps requiring socket connections work (portsnap, fetch,
ssh, svn, etc).
I'll provide more info if requested.
For the time being I'll have to move to svn for the time being
because the project supports SVN as well as CVS.
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0812131831ucc9cd71scabbfa045192242e>