[Qt-creator] Remote GDB debugging.

[Tim Hutt]

Ok I finally got GDB built!

I went for targets=arm-none-eabi, and I also had to change line 113 of the
Makefile to:

 cp -r
${staging}/gdb-${version}-${targets}/gdb/data-directory/{python,syscalls}
${targetdir}/data-directory && \

Previously the ${targets} was hardcoded as pc i686 etc. Obviously that's
not quite correct since ${targets} can apparently be multiple values, but
it works for now.

Another problem is that you have to add  --data-directory data-directory on
the command line when you run it. It seems it isn't configured correctly to
look for it by default. Not sure what to do about that.

This page:
https://sourceware.org/gdb/onlinedocs/gdb/Data-Files.html#Data-Files
 says you can use a configure-time option --with-gdb-datadir, but I'd put
money on it not supporting relative paths (no-one in Linux-land seems to
acknowledge believe in relative paths).

Anyway I tried it out, and sadly get the same error "message":
[image: Inline images 1]
Sad face.

By the way I found a link that tries to explain how the whole arm-none-eabi
thing actually works, because it isn't really documented anywhere and
doesn't really seem to be consistent: http://kunen.org/uC/gnu_tool.html


On 16 June 2014 14:15, Tim Hutt <tdhutt at gmail.com> wrote:

> Oh ok I will give that a go.
>
>
> On 16 June 2014 11:56, Orgad Shaneh <orgads at gmail.com> wrote:
>
>> On Mon, Jun 16, 2014 at 1:41 PM, Tim Hutt <tdhutt at gmail.com> wrote:
>>
>>> I may be wrong, but I don't think that actually work with ARM Cortex-M0
>>> chips. Otherwise why does this exist?:
>>>
>>>     https://launchpad.net/gcc-arm-embedded
>>>
>>> Sadly, gcc-arm-embedded does not support being built on Windows (I've
>>> now tried, look at this excerpt from the build script):
>>>
>>> # Set variables according to real environment to make this script can run
>>> # on Ubuntu and Mac OS X.
>>> ...
>>> if [ "x$uname_string" == "xlinux" ] ; then
>>> ...
>>> elif [ "x$uname_string" == "xdarwin" ] ; then
>>> ...
>>> else
>>>     error "Unsupported build system : $uname_string"
>>> fi
>>>
>>> Maybe I can add MingW support to their build system, but I doubt it's
>>> going to be easy! (Otherwise I imagine they'd have done it already.)
>>>
>>> Cheers,
>>>
>>> Tim
>>>
>>>
>>> On 16 June 2014 11:22, Fatih Aşıcı <fatih.asici at gmail.com> wrote:
>>>
>>>> On Monday 16 June 2014 12:29:34 Tim Hutt wrote:
>>>> > Hi, thanks. I tried QtCreator 3.0.1, but sadly I get this unhelpful
>>>> error
>>>> > "message":
>>>> >
>>>> > [image: Inline images 1]
>>>> >
>>>> > Oh well. I guess I'll try and build the Arm GCC with python at some
>>>> point,
>>>> > but probably not for a while - cross-compiling a cross-compiler that
>>>> > depends on python doesn't sound like my idea of fun!
>>>>
>>>> You can try the makefiles in qt-creator repository:
>>>>
>>>>
>>>> https://qt.gitorious.org/qt-creator/qt-creator/source/17febac88b8ecfde9a5502b27f72b58ab4277165:dist/gdb
>>>>
>>>> You need to change the "targets" variable (e.g. targets=arm-none-eabi
>>>> msp430-elf).
>>>>
>>>> Regards,
>>>> Fatih
>>>>
>>>
>>>
>>> _______________________________________________
>>> Qt-creator mailing list
>>> Qt-creator at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>
>>>
>> You don't need to build gcc in order to use gdb. Those are separate
>> projects.
>>
>> GDB can be built for any target using MSYS+MinGW. Set targets in
>> Makefile.mingw and run make -f Makefile.mingw.
>>
>> - Orgad
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140617/73c1c8d1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 8787 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140617/73c1c8d1/attachment.png>