On Dec 3 16:04, Stefan Bylund wrote: > I looked at the cygwin change list from 1.5.19-4 to 1.5.20-1 > (http://cygwin.com/ml/cygwin-announce/2006-07/msg00000.html) and noticed > the following signal-related changes: > > * cgf: When sending signals, assume that any code which is not directly > associated with a DLL or an executable is user code. > > * cgf: Pass cygwin signals to gdb. Fix the dreaded SIGSEGV found in some > pthread functions. > > * corinna: Implement sigignore and sigset. > > * cgf: Make SA_RESTART sigaction flag work more like linux. > > It seems that one or more of the changes listed above (or some other > change(s) described in > http://cygwin.com/ml/cygwin-announce/2006-07/msg00000.html) is the cause of > this problem. It is a bit ironic that one of the changes mentions passing > cygwin signals to gdb since it is exactly this functionality that is now > broken but, from our experience, worked in 1.5.19-4. > > I'm cross posting this mail to the CDT mailing list as well, since there > may be other Eclipse/CDT users interested in this issue. > > Is there anything I can do to help in finding out why versions starting
The best help would be a really simple testcase, written in plain C, using the minimum amount of code to reproduce the problem. This would allow to track it down without having to play time machine. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
