RE: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread Richard Schmitt
21, 2006 7:54 PM To: cygwin@cygwin.com Subject: Re: GDB and Cygwin SIGSEGV revisited [EMAIL PROTECTED] wrote: > On Sun, May 21, 2006 at 06:40:45PM -0400, Christopher Faylor wrote: >> Again, Brian answered the question correctly. Building a 6.4 version >> of gdb is not going to solv

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread Larry Hall (Cygwin)
[EMAIL PROTECTED] wrote: On Sun, May 21, 2006 at 06:40:45PM -0400, Christopher Faylor wrote: Again, Brian answered the question correctly. Building a 6.4 version of gdb is not going to solve this problem. cgf Okay, so what is the exact answer? Is it: CVS HEAD build of gdb will fix the issue

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread clayne
On Sun, May 21, 2006 at 06:40:45PM -0400, Christopher Faylor wrote: > Again, Brian answered the question correctly. Building a 6.4 version of > gdb is not going to solve this problem. > > cgf Okay, so what is the exact answer? Is it: CVS HEAD build of gdb will fix the issue? -cl -- Unsubscrib

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread Christopher Faylor
On Sun, May 21, 2006 at 03:31:13PM -0700, [EMAIL PROTECTED] wrote: >On Sun, May 21, 2006 at 04:39:18PM -0400, Christopher Faylor wrote: >>>6.4 works, but I've found that no matter what, initializing the >>>following: >> >>There is no way that 6.4 is going to fix this problem since, as Brian >>noted

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread clayne
On Sun, May 21, 2006 at 04:39:18PM -0400, Christopher Faylor wrote: > >6.4 works, but I've found that no matter what, initializing the > >following: > > There is no way that 6.4 is going to fix this problem since, as Brian > noted, its release predates the fix that I checked in to deal with the >

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread Christopher Faylor
On Sun, May 21, 2006 at 09:34:46AM -0700, [EMAIL PROTECTED] wrote: >On Sun, May 21, 2006 at 07:14:52AM -0700, Brian Dessent wrote: >>Richard Schmitt wrote: >> >>>- downloaded the latest gdb (6.4), built it and installed it. [...] >>>doesn't suffer from this problem? The issue was fixed in CVS ear

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread clayne
On Sun, May 21, 2006 at 07:14:52AM -0700, Brian Dessent wrote: > Richard Schmitt wrote: > > > - downloaded the latest gdb (6.4), built it and installed it. > > [...] > > doesn't suffer from this problem? The issue was fixed in CVS earlier > > this year. But do note that it requires functionality

Re: GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread Brian Dessent
Richard Schmitt wrote: > - downloaded the latest gdb (6.4), built it and installed it. > [...] > doesn't suffer from this problem? The issue was fixed in CVS earlier > this year. But do note that it requires functionality not present in 6.4 won't do, it's too old. The fix was committed in Febr

GDB and Cygwin SIGSEGV revisited

2006-05-21 Thread Richard Schmitt
I've seen a lot of discussion on issues with SIGSEGV and pthread mutexes with GDB under cygwin. I was very hopeful when I saw a reply by Brian Dessent that said this was fixed if I downloaded the latest gdb and a cygwin snapshot. Maybe there's something else I haven't downloaded but here's what I