[Qt-creator] Remote GDB debugging.

[Tim Hutt]

I'm not actually using openocd; I'm using the Segger gdb server. Maybe that
makes no difference though.

If you read the gdb commands QtCreator executes (see earlier email) you can
see that:

1. The init commands (monitor halt, etc.) are never executed.
2. If never runs "remote localhost:2331" or whatever.
3. It still seems to think it is using an x86 ABI
4. The --data-directory is not passed correctly as I previously thought
(though I guess this doesn't matter for now).

Clearly this is all wrong. I also have no idea what to put in the "Source"
and "Target" options of the source mapping. What am I mapping to what?

Thanks for the help by the way!

Cheers,

Tim


On 17 June 2014 12:18, Tim Sander <tim at krieglstein.org> wrote:

> Hi Tim
> Am Dienstag, 17. Juni 2014, 11:58:28 schrieb Tim Hutt:
> > I'm not using a remote build server.
> Well you are using the openocd gdbserver, which acts like a remote server
> to
> qtcreator.
>
> > The device type is Bare Metal. (Ignore the compiler setting below - I've
> > overridden it in my build file; I'll fix this at some point.)
> So you should use f5 or the debug button to start. Otherwise the init
> commands
> will not be executed.
>
> I would suggest to replace your init commands with:
> monitor reset halt
> load
> monitor reset halt
>
> QtCreator expects the target to be halted after the initialisation. Also
> doing
> a montior reset halt befor loading makes sure your device is in a defined
> state.
>
> Best regards
> Tim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140617/23a36064/attachment.html>