[Qt-creator] 64 bit gdb-python27.exe

[andy fillebrown]

On Fri, Mar 11, 2011 at 1:02 PM, andy fillebrown
<andy.fillebrown at gmail.com> wrote:
> On Fri, Mar 11, 2011 at 12:29 PM, andy fillebrown
> <andy.fillebrown at gmail.com> wrote:
>> On Fri, Mar 11, 2011 at 10:40 AM, André Pönitz <andre.poenitz at nokia.com> wrote:
>>> On Friday 11 March 2011 04:28:39 ext andy fillebrown wrote:
>>>> On Thu, Mar 10, 2011 at 10:24 PM, andy fillebrown
>>>> <andy.fillebrown at gmail.com> wrote:
>>>> > On Thu, Mar 10, 2011 at 11:22 AM, Andre Poenitz
>>>> > <andre.poenitz at mathematik.tu-chemnitz.de> wrote:
>>>> >> On Wed, Mar 09, 2011 at 11:54:55PM -0500, andy fillebrown wrote:
>>>> >>> On Wed, Mar 9, 2011 at 11:15 AM, Daniel Molkentin
>>>> >>> <daniel.molkentin at nokia.com> wrote:
>>>> >>> > On 3/9/2011 10:44 AM, ext andy fillebrown wrote:
>>>> >>> >>> ftp://ftp.qt.nokia.com/misc/gdb/7.2/  or the Qt SDK 1.1 beta installer.
>>>> >>> >>
>>>> >>> >> AFAIK, the mingw gdb downloads at ftp.qt.nokia are all 32 bit.  I need
>>>> >>> >> a 64 bit version.
>>>> >>> >>
>>>> >>> >> ~ af
>>>> >>> > I have updated
>>>> >>> > ftp://ftp.qt.nokia.com/misc/gdb/7.2/qtcreator-gdb-7.2-mingw-x86.zip to
>>>> >>> > include a gdb binary for the x86_64 target (gdb-x86_64-pc-mingw32.exe).
>>>> >>> > Don't be confused by the fact that the binary itself is still compiled
>>>> >>> > for 32 bit as the host platform (mostly for pragmatic reasons, we can
>>>> >>> > reuse the 32 bit python, there is no real benefit to ship another python
>>>> >>> > lib). It's compiled to debug 64 bit targets nevertheless. Please test it
>>>> >>> > with a Qt Creator for 2.2 (preferred) or master branch.
>>>> >>> >
>>>> >>> > Note that all I verified is that the binary starts and python can be
>>>> >>> > invoked. Enjoy :)
>>>> >>>
>>>> >>> In QtCreator, I'm getting ...
>>>> >>>
>>>> >>> 20-exec-run
>>>> >>> >20^error,msg="Don't know how to run.  Try \"help target\"."
>>>> >>> dDon't know how to run.  Try "help target".
>>>> >>> dNOTE: ENGINE RUN FAILED
>>>> >>
>>>> >> Please attach the full log.
>>>> >
>>>> > Here is the log from the TDM MinGW prebuilt binary.  I've also tested
>>>> > with a MinGW-w64 prebuilt binary, but it shows similar output.  I'll
>>>> > send it later if you want.
>>>> >
>>>> > Thanks for looking into this.
>>>> >
>>>> > Cheers,
>>>> > ~ andy.f
>>>>
>>>>
>>>> Note that the specified gdb startup script contains one line, which is
>>>> "b qFatal" -- without the quotes.
>>>
>>> Does it change if you don't use the startup script (and later perhaps
>>> set the breakpoint in the breakpoint view directly)?
>>
>> No, and gdb reports the same error when run from the command line with
>> target exec set to the binary being debugged in the log.
>>
>
> I've attached two more logs.  The log ending with qt-gdb uses the
> build from the ftp.qt.nokia.com site, and the log ending with tdm-gdb
> uses the build that came with the precompiled mingw-w64 package from
> twilight dragon media.  AFAIK, the tdm gdb is 7.1, and it is not
> python enabled -- but it does start up.  Other than not being python
> enabled, the only problem I'm having with the tdm version is it won't
> stop at breakpoints in shared libraries.
>
> Hope that helps,
> ~ andy.f
>

If I can get 32 bit Qt libs built with TDM MinGW, and the 32 bit gdb
at ftp.qt.nokia.com still can't load the app, then it may be a hint as
to what's wrong with the 64 bit gdb at ftp.qt.nokia.com.

I tried to force 32-bit compilation on the TDM MinGW toolchain, but
the linker said QtCored and QtGui were incompatible since they were
built with the 32-bit MinGW found at ftp.qt.nokia.com.  To build
compatible Qt libs, I need to know how do I force mingw-w64 to compile
32-bit binaries from the command line.

How do I pass -m32 to gcc in the call to mingw32-make?

~ af