[Qt-creator] Remote GDB debugging.

[Tim Hutt]

By the way Tim, it would be nice if the behaviour of Run vs Debug was
changed slightly. At the moment it seems Run is just aliased to Debug, but
I think it would make more sense if Run compiled and downloaded the
firmware (via GDB), reset and start the device, and the disconnect from GDB
while leaving the CPU running.

Maybe that's not easy, and I guess it isn't a huge issue.


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

> Hi Tim
>
> Am Mittwoch, 18. Juni 2014, 11:12:48 schrieben Sie:
> > Oh wow I finally got it to work! The key was to use the initialisation
> > commands provided by Nordic (who make the nRF51822)!:
> >
> > mon speed 10000
> >
> > mon endian little
> >
> > mon flash download = 1
> >
> > mon flash device = NRF51822
> >
> > mon reset 0
> >
> >
> > However, I have no discovered a segfault in QtCreator! It crashes
> > ("qtcreator.exe has stopped working") if you do either of:
> >
> >
> > 1. Manually pause program execution.
> >
> > 2. Add a breakpoint while the program is running.
> I guess thats a Windows problem, but that can be omitted if you *enable*
> Tools->Options->Debugger->GDB Extended->"Use asynchronous mode to control
> the
> inferior".
>
> > So close!
> On the mark with the above config change :-).
>
> > On 18 June 2014 10:58, Tim Hutt <tdhutt at gmail.com> wrote:
> > > The same files is generated in both cases though... If it's checking
> for
> > > the string "application" in the types list, I think that should just be
> > > removed. If it's seeing if the "last" build item is an "application",
> or
> > > if
> > > any of the explicitly specified types are "application", then I think
> that
> > > should be changed to search the entire build tree for the "application"
> > > node.
> > >
> > > Anyway...
> > >
> > > I forgot to mention that I also get this error when clicking the debug
> > > button:
> > >
> > > [image: Inline images 1]
> > >
> > > What is the "inferior"?
> > >
> > > I also tried using "break main.cpp:51" from the official Gnu ARM
> Embedded
> > > install (which is the one the chip maker recommend so I know it should
> > > work). It had the same effect as break-insert did from QtCreator... So
> > > maybe it's just that Eclipse (what they use) knows to use monitor setbp
> > > instead of break? Or maybe they tell gdb how break should behave?
>
> You should also *disable* Tools->Options->Debugger->GDB->"Show a message
> box
> when receiving a signal" to get rid of the message box when hitting a
> breakpoint.
>
> Best regards
> Tim
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140618/3fcf3965/attachment.html>