This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Slightly offtpic: why svn stubbornly refuses to listen to ctrl-c?!?
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Date: Fri, 15 Jan 2010 15:47:29 +0000
- Subject: Re: Slightly offtpic: why svn stubbornly refuses to listen to ctrl-c?!?
- References: <4B50711D.3030506@oracle.com>
Paolo Carlini wrote:
> Hi,
>
> I mean, why a well designed application should refuse to listen to
> ctrl-c when something goes wrong? Why every time for some reason it gets
> stuck, I have to kill it from another shell? That's definitely annoying.
>
> Paolo.
Hmm, this is also Debian bug #502222, 461873 and 266973
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/f4768634a6043e7d
also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461873
http://www.mail-archive.com/debian-bugs-closed@lists.debian.org/msg19117.html
Looks like there's a read loop in libapr that is deliberately designed to
continue if it gets EINTR. Perhaps a somewhat crude mechanism for
guaranteeing atomicity/preventing corrupted sandbox? Ah,
http://subversion.open.collab.net/ds/viewMessage.do?dsForumId=4&viewType=browseAll&dsMessageId=817
says that there are cancellation-safe checkpoints in processing, and svn
defers ctrl-c until the next one comes up. You probably need to talk to
upstream if there are places where it's showing an unacceptably long delay
between checkpoints. (Also, make sure you're using the latest version of svn
available, as this behaviour has been worked on during 1.5 timeframe).
cheers,
DaveK