On Mon, Mar 14, 2011 at 4:40 AM, André Pönitz <[email protected]> wrote: > On Saturday 12 March 2011 11:46:56 ext andy fillebrown wrote: >> I rebuilt gdb with --target=x86_64-w64-mingw32 and I get the original >> "Don't know how to run" error. >> >> I still suspect this is a sjlj/dw2 issue, so I'm going to try building >> gdb with TDM-MinGW64 linked to Python27-64, to see if it works. > > Would be nice if this succeeds, but from my side it looks like "out of scope" > by now. I think it's the distribution's responsibility to ship debuggers with > the "usual" features, and for gdb 7.x this certainly includes python. > > Andre'
I hacked on the gdb makefiles and sources to get it to compile and it seems I've done something wrong ...not surprising since it was my first time with the gdb sources. The gdb.exe I built runs, but there's some Python issue causing a traceback and "python print 23" doesn't work. Please let me know if you've any ideas regarding the traceback: TypeError: type 'gdb.Symbol' participates in gc and is a base type but has inappropriate tp_free slot Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'gdb' is not defined Maybe because I removed the -D$(BINDIR) CFLAG in the bfd makefile? ... or maybe Daniel can get it working on his end. Cheers, ~ andy.f _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
