[Qt-creator] Remote GDB debugging.

[Tim Hutt]

Yes, that worked! Only remaining flaw is that you get the previous dialog I
posted (about SIGTRAP) every time you pause the execution. I can live with
that though.

The crash is clearly still a bug in Qt Creator which would be nice to fix.
Brief interlude though:

This site is amazing!! Why can't Gitorious do this:
http://code.woboq.org/qt5/qt-creator/

Anyway, here's where the problem is:

In gdbengine.cpp:

void GdbEngine::interruptInferior()
{
    QTC_ASSERT(state() == InferiorStopRequested,
        qDebug() << "INTERRUPT INFERIOR: " << state(); return);

    if (usesExecInterrupt()) {
        postCommand("-exec-interrupt", Immediate);
    } else {
        showStatusMessage(tr("Stop requested..."), 5000);
        showMessage(_("TRYING TO INTERRUPT INFERIOR"));
        if (HostOsInfo::isWindowsHost() && !m_isQnxGdb) {
            QTC_ASSERT(state() == InferiorStopRequested, qDebug() <<
state(); notifyInferiorStopFailed());
            QTC_ASSERT(!m_signalOperation, notifyInferiorStopFailed());
            m_signalOperation = startParameters().device->signalOperation();

This line goes to baremetaldevice.cpp:

DeviceProcessSignalOperation::Ptr BareMetalDevice::signalOperation() const
{
    return ProjectExplorer::DeviceProcessSignalOperation::Ptr();
}

Which basically returns NULL.




On 18 June 2014 14:25, Fatih Aşıcı <fatih.asici at gmail.com> wrote:

> On Wednesday 18 June 2014 13:12:48 Tim Hutt wrote:
> > 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.
>
> Selecting "Options->Debugger->GDB Extended->Use asynchronous mode to
> control the inferior"
> should fix this.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140618/194858f4/attachment.html>