Re: Debugging with cygwin tools

2007-10-08 Thread Christopher Faylor
On Mon, Oct 08, 2007 at 07:33:41PM +, David Gangola wrote: >Alberto Luaces udc.es> writes: > >> >> El Monday 08 October 2007 15:08:25 Greg Chicares escribi??: >> > I believe the MinGW gdb repository == the Cygwin repository: >> > ?? http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/?cvsroo

Re: Debugging with cygwin tools

2007-10-08 Thread David Gangola
Alberto Luaces udc.es> writes: > > El Monday 08 October 2007 15:08:25 Greg Chicares escribió: > > I believe the MinGW gdb repository == the Cygwin repository: > >   http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/?cvsroot=src > > > > However, you seek a patch that apparently hasn't been app

Re: Debugging with cygwin tools

2007-10-08 Thread Alberto Luaces
El Monday 08 October 2007 15:08:25 Greg Chicares escribió: > I believe the MinGW gdb repository == the Cygwin repository: >   http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gdb/?cvsroot=src > > However, you seek a patch that apparently hasn't been applied yet. > The "bugs" tracker cited above con

Re: Debugging with cygwin tools

2007-10-08 Thread Greg Chicares
On 2007-10-08 12:04Z, Alberto Luaces wrote: > El Friday 05 October 2007 22:30:02 René Berber escribió: [...] >> Same probem has been reported in MingW: >> >> https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1500271&group_ >> id=2435 >> >> the most recent message (2 months ago) even ment

Re: Debugging with cygwin tools

2007-10-08 Thread Alberto Luaces
El Friday 05 October 2007 22:30:02 René Berber escribió: > Doug Coleman wrote: > > Here is 'info files' in gdb. There have been other posts about the same > > problem, but no resolution afaik: > > http://cygwin.com/ml/cygwin/2007-03/msg00182.html [snip] > > My only guess, by the 0x77d41000 address

Re: Debugging with cygwin tools

2007-10-05 Thread René Berber
Doug Coleman wrote: > So I attached to the running process and that works! Nice one, nothing maps to the infamous address (in fact everyting is way above that -- with one more digit in the address), seems like the gdb bug report at MingW might be in the right track. > Here is an info files from

Re: Debugging with cygwin tools

2007-10-05 Thread René Berber
Doug Coleman wrote: > Here is 'info files' in gdb. There have been other posts about the same > problem, but no resolution afaik: > http://cygwin.com/ml/cygwin/2007-03/msg00182.html Yes, same problem. > $ gdb ./factor-nt > GNU gdb 6.5.50.20060706-cvs (cygwin-special) > Copyright (C) 2006 Free S

Re: Debugging with cygwin tools

2007-10-05 Thread Doug Coleman
René Berber-2 wrote: > > Doug Coleman wrote: > >> I'm having the exact same problem on win64 with gdb. The PATH variable >> has >> been set manually to avoid possible syntax errors, but the same problem >> exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as >> missing. gd

Re: Debugging with cygwin tools

2007-10-05 Thread Doug Coleman
René Berber-2 wrote: > > Doug Coleman wrote: > >> I'm having the exact same problem on win64 with gdb. The PATH variable >> has >> been set manually to avoid possible syntax errors, but the same problem >> exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as >> missing. g

Re: Debugging with cygwin tools

2007-10-05 Thread René Berber
Doug Coleman wrote: > I'm having the exact same problem on win64 with gdb. The PATH variable has > been set manually to avoid possible syntax errors, but the same problem > exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as > missing. gdb works on my win32 computer. > > An

Re: Debugging with cygwin tools

2007-10-05 Thread Doug Coleman
I'm having the exact same problem on win64 with gdb. The PATH variable has been set manually to avoid possible syntax errors, but the same problem exists when I don't shorten the PATH. Cygcheck doesn't list any dlls as missing. gdb works on my win32 computer. Any other ideas? Doug $ uname -a

Re: Debugging with cygwin tools

2007-10-04 Thread René Berber
Alberto Luaces Fernández wrote: [snip] > thanks for the tips, I will check the PATH and look for missing DLLs > then, although my program is nothing more than a main function > dereferencing a null pointer, so it should not have any special > dependencies. It doesn't. > The missing DLL message w

RE: Debugging with cygwin tools

2007-10-04 Thread Alberto Luaces Fernández
Dave Korn <[EMAIL PROTECTED]>: On 04 October 2007 16:15, René Berber wrote: Alberto Luaces wrote: I am just starting to learn how to use the debugging tools available in Cygwin. To do so, I have a test program deliberately designed to crash: [snip] I have compiled it with debugging informati

RE: Debugging with cygwin tools

2007-10-04 Thread Dave Korn
On 04 October 2007 16:15, René Berber wrote: > Alberto Luaces wrote: > >> I am just starting to learn how to use the debugging tools available in >> Cygwin. To do so, I have a test program deliberately designed to crash: >> [snip] I have compiled it with debugging information: >> >> g++ -g -O0 -

Re: Debugging with cygwin tools

2007-10-04 Thread René Berber
Alberto Luaces wrote: > I am just starting to learn how to use the debugging tools available in > Cygwin. To do so, I have a test program deliberately designed to crash: [snip] > I have compiled it with debugging information: > > g++ -g -O0 -o core core.cpp > > Then I try to run it with gdb: >