Should I expect any problems when running gdb/insight on Cygwin, debugging cross-compiled binaries?
I'm cross-compiling on Linux (-g -O0), and copying the binaries to Cygwin, together with the same source tree that I used on Linux. When I run insight on Cygwin, the initial window displays only assembler output. More info: 1 - Insight can find and display the source files, but can't set a breakpoint in the source file (and nor can plain gdb) 2 - if I change to the same directory as the file that contains main, and run 'gdb myprog.exe', it makes no difference. If I enter 'break foo.cc:100' gdb replies "No line 100 in file 'foo.cc'". 3 - The source directory tree on Cygwin is identical to the source directory tree on Linux, except that one is rooted at 'C:'. However, if I run 'pwd' from the gdb console then the path reported is the Cygwin path, which is identical to the Linux path. 4 - the code definitely has debug info in it - it's much larger than the optimised version. Thanks - Paul ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
