Re: gcc + gdb + breakpoint => SIGSEGV

2008-03-03 Thread Ray Hurst
Dave, I downloaded the GDB 6.7.1 source and built it. Ray Dave Ohlsson wrote: Hi, This is what I did: 1) Removed several applications (including MtSQL 5.0) and rebooted. => no help. 2) Downgraded gdb from version 6.5.50.20060706-cvs to version 6.3.50_2004-12-28-cvs (I couldn't find gdb v

RE: gcc + gdb + breakpoint => SIGSEGV

2008-03-03 Thread Dave Ohlsson
Hi, This is what I did: 1) Removed several applications (including MtSQL 5.0) and rebooted. => no help. 2) Downgraded gdb from version 6.5.50.20060706-cvs to version 6.3.50_2004-12-28-cvs (I couldn't find gdb version 6.7.1 that Ray mentioned in his post). => IT WORKS! Thanks! -- dav

RE: gcc + gdb + breakpoint => SIGSEGV

2008-03-03 Thread Dave Korn
On 03 March 2008 11:31, Dave Ohlsson wrote: > Update to my original post: > > The same problem does NOT occur on my second PC, where I also > have Windows XP + Cygwin and EXACTLY the same versions of gcc > (3.4.4) and gdb (6.5.50.20060706-cvs). On my second PC, I get a correct > behavior: I t

RE: gcc + gdb + breakpoint => SIGSEGV

2008-03-03 Thread Dave Ohlsson
Update to my original post: The same problem does NOT occur on my second PC, where I also have Windows XP + Cygwin and EXACTLY the same versions of gcc (3.4.4) and gdb (6.5.50.20060706-cvs). On my second PC, I get a correct behavior: gdb a.exe (gdb) list 1 int main(int argc,

Re: gcc + gdb + breakpoint => SIGSEGV

2008-03-02 Thread Ray Hurst
I had the same issue a couple of weeks ago. I never figured it out. I ended up updating the compiler to v4.2.3 then I updated gdb to v6.7.1. Everything started working. You might try just updating gdb and see what happens. The issue was only with cygwin. The same versions you have below ran un