This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: (call-process ...) hangs in emacs
- From: Peter Hull <peterhull90 at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 5 Aug 2014 14:33:39 +0100
- Subject: Re: (call-process ...) hangs in emacs
- Authentication-results: sourceware.org; auth=none
- References: <53DB8D23 dot 7060806 at alice dot it> <CAK9Gx1cjj-7cDP7CunD7Bxz35L+SU9+4Ro3HRot5cwjcArudOA at mail dot gmail dot com> <20140801133225 dot GD25860 at calimero dot vinschen dot de> <53DEDBBA dot 20102 at cornell dot edu> <20140804080034 dot GA2578 at calimero dot vinschen dot de> <53DF8BDC dot 8090104 at cornell dot edu> <20140804134526 dot GK2578 at calimero dot vinschen dot de> <53E0CC2D dot 4080305 at cornell dot edu>
On Tue, Aug 5, 2014 at 1:21 PM, Ken Brown <kbrown@cornell.edu> wrote:
> - pthread_mutex_init (&_malloc_mutex, NULL);
> - pthread_mutex_init (&_aligned_blocks_mutex, NULL);
> + pthread_mutexattr_t attr1, attr2;
> + pthread_mutexattr_settype (&attr1, PTHREAD_MUTEX_NORMAL);
> + pthread_mutexattr_settype (&attr2, PTHREAD_MUTEX_NORMAL);
> + pthread_mutex_init (&_malloc_mutex, &attr1);
> + pthread_mutex_init (&_aligned_blocks_mutex, &attr2);
> pthread_atfork (malloc_atfork_handler_prepare,
> malloc_atfork_handler_parent,
> malloc_atfork_handler_child);
Does there need to be a 'pthread_mutexattr_init' in there? I don't
think that's the problem though...
Pete
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple