Hello Paul, 2011/2/11 Paul Leder <[email protected]>: > Should I expect any problems when running gdb/insight on Cygwin, > debugging cross-compiled binaries?
No, in general this should work, beside that you have to know that file paths to sources can be different between POSIX/MS file-naming. But this can be maybe work-a-rounded by using gdb-server for debugging, but well, I didn't played much by it. More of interest are here the version of gcc, gdb, and binutils you were using for generating objects/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) Hmm, I am not that much familiar here with insight, but I know that gdb (if compiled with libexpat support) works in general. > 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'". Well, this seems to be a path issue you see here. Regards, Kai ------------------------------------------------------------------------------ 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
