SegFault accessing `ui->tabWidget` but there is warning about vtable entries

JoeCFD

click make clean and rebuild your app( better cd the build dir and do make distclean, then click run qmake)
Set a break point at the beginning of that func and show which line causes crashes.

mrjj

Hi
It all looks pretty normal.

If you open one of the examples and run. Does it compile without any such errors ?

Do you link any other libs via the pro file ?

I have seen this error message with some nasty pointer errors.
Do you do anything interesting with any of the Widgets ?
Like keeping them in a list and also insert into a form or anything like that ?

enjoysmath

@mrjj Nope, nothing unusual. What's causing the vtable errors?

mrjj

Hi
well actually the normal one is
undefined reference to `vtable for
which can be caused by not implementing virtual functions or lack
QOBJECT macro among other things.

But this error
cant find Linker symbol for virtual table
seems to be linked to both virtual function and dangling pointers.

If i had to guess , it would be on some kind of pointer error.

When it crashes, the call stack gives no hint on what it was doing ?

enjoysmath


 void MainWindow::zoomCurrentWidget(int times)
 {
     auto widget = ui->tabWidget->currentWidget();
 
     if (widget) {
         auto view = dynamic_cast<ZoomableView*>(widget);
 
         if (view)
             view->zoomTimes(times);
     }
}

@mrjj It's in this function where the SegFault happens. It was usually on the first line, but later the Qt Creator had me believing it was also happening further down.

enjoysmath

@mrjj It's definitely the first line. It doesn't return a working pointer to the QTabWidget, although QtCreator, when you hover over the code in Debug mode, shows that it's a QTabWidget* typed value. So there is a bug with QtCreator. I'm doing nothing special to induce this bug. Does this mean I have to go back to PyQt5 to finish my project? I thought C++ would be a lot nicer for handling large graphics scenes, but apparently there are just too many bugs.

Christian Ehrlicher

Then you killed the tabWidget somewhere else already.

enjoysmath

@Christian-Ehrlicher that's the first time I'm accessing the QTabWidget.

enjoysmath

@Christian-Ehrlicher

Okay, you were right :)

I was doing this:

```

MainWindow w;
w.setCentralWidget(&view);
w.show();


Which would of course wipe out the QWidget created from the UI Designer.  Thank you!

:)

mrjj

@enjoysmath
Hi
Just as a note:

Does this mean I have to go back to PyQt5 to finish my project?

Python version is a binding using the c++ classes so if it was a Qt bug same thing would happen in PyQt5.

enjoysmath

@mrjj @Christian-Ehrlicher @JonB @JonB

Thanks all who helped me solve this. I will make it my duty to write an awesome software tool for my users.

-EnjoysMath