On Fri, Feb 11, 2011 at 9:43 AM, NightStrike <[email protected]> wrote: > On Fri, Feb 11, 2011 at 8:22 AM, Paul Leder <[email protected]> wrote: >> Executable is 32-bit, and Cygwin/gdb is 32-bit. >> >> The gdb is the current version from Cygwin, which is 6.8.0. The Cygwin >> gcc is 3.4.4. >> >> I compiled with a Linux binary distribution which I downloaded last week >> (I don't have access to that machine at the moment, but the gcc version >> is ~4.5.2). >> >> Sounds like I may have to rebuild the cross-compiler to produce >> something more palatable to Cygwin... what do you think? It seems to me >> that debugging is the weak link in this chain. I guess I'll have to have >> a look at gdbserver, but then I'll need to make sure my dev system is >> running a compatible version of gdb. Would it make sense for mingw-w64 >> to distribute a binary host gdb along with the binary cross tools? >> > > It'd be easier to rebuild gdb.... > > And, we do offer a Win64-natively hosted gdb. >
Hmm.............. gdb can be built with top level configure just by adding it to the source tree. It can be configured with host/target to control where it runs and what it debugs for. This would be very handy for instance for going from cyg32 to win64. Maybe we should start doing this. It won't add too much more time to the builds. Heck, those cygwin builds are already taking 15 hours... what's another one? ------------------------------------------------------------------------------ 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
