I should note that the dialog can be ignored and messages will collect there without requiring an escape or clicking on 'ok'. But for continuity sake, this really ought to pop up as one of the 'output' panes.

Also, the message is never useful, because it does not identify where it was looking for a method, function or member when the error occurred.

For detailed investigation I need GDB log attached. Without log I cannot understand what I should fix:(

I see other GDB error in such case:


#include <vector>

using namespace std;

struct A {

    A(float cost) :
    cost(cost) {
    }

    float cost;
};

struct B {

    B(float c) :
    c(c) {
    }

    float c;
};

void test(vector<B> *v0, vector<A> *v1) {
    for (vector<B>::iterator i = v0->begin(); i != v0->end(); i++) { // set line breakpoint
        i->c += 0.1f;
    }
    for (vector<A>::iterator i = v1->begin(); i != v1->end(); i++) {
        i->cost += 0.1f;
    }
}

int main() {
    vector<B> v0;
    v0.push_back(B(0.3f));

    vector<A> v1;
    v1.push_back(A(0.0f));
    v1.push_back(A(0.1f));
    test(&v0, &v1);
    return 0;
}

Scenario:
- Stop debugger in test()
- Add i->c and i->cost variables to Variables tab
- Press 3-4 times
==> I see such Debugger Error window:
Type A has no component named c.
Type A has no component named c.

missed:
- Press F8 key 3-4 times

Other scenario:
struct A {
    A(float _a) : a(_a) {}
    float a;
};
struct B {
    B(float _a) : b(_a) {}
    float b;
};
int main() {
    {
        A* a = new A(0.1f);
    }
    {
        B* a = new B(0.2f);
    }
    return 0;
}

Variables 'a->a' and 'a->b'

Integrated into 'main-silver', will be available in build *201708150001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/33c0585654f8
User: Maria Dalmatova <mromashova@netbeans.org>
Log: fixed bz#268815 - in debugger: frequent debugger errors make stepping painful
1) New Debugging options is added under Tools->Options->C/C++->Debugging Options named "Do not popup debugger errors", when it is turned on the debugger errors will be printed in Debugger Errors window. This window will be opened in output mode but will not request focus. This window can be opened using Window->Debugging->Debugger Errors menu
2) The error message printed in error dialog (or text pane of Debugger Errors window) now contains command the error is occurred for
3) New Debugger Log functionality is added. If debugger provides log file (as GDB does) it can be opened as a part of Output using Windows->Debugging->Debugger Log. This log has the same functionality IDE Log has.