Brian was right. I've downloaded gdb 6.5.60.20060516 (the latest) and built
it. It runs fine with cygwin1.dll 20060521. No more sigsegv's. Thanks.
Rich
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Larry Hall (Cygwin)
Sent: Sunday, May 21, 2006 7:5
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
21, 2004 at 11:04:12PM -0400, Richard Schmitt wrote:
I know, I've seen the posts on this issue but I'm a little suprised that
a real solution hasn't been found.
Don't be surprised. We just don't like you and are all cackling with glee
at your discomfort.
What o
I know, I've seen the posts on this issue but I'm a little suprised that
a real solution hasn't been found. I recently upgraded cygwin and
debugging basically doesn't work. The 'work-around' was to just
continue gdb when it received one of these
segfaults. Well, that workaround doesn't really
4 matches
Mail list logo