As I said, Its no real error, the application does not terminate or interrupt.

SpecialObject goes out of scope right after you insert it into your hash. Afterwards its contents is undefined.

You have to create your SpecialObject on the heap, because this way it gets deleted after you leave the addNewData function.

Ok, and as far as I know every with new created pointer should be deleted by programmer later on.

does not make any sence right? Shall I delete all those SpecialObjects pointers in the destructor later? How would you handle that?

A bit difficult to give advice with so little information. If SpecialObject is a small class, and it makes sense to pass SpecialObject objects around by value, then the code you have written should be OK. If not, then you must create the objects on the heap, using new, and then delete them when you no longer need them, e.g. when/before the QHash is destroyed.

Looks to me like you have not properly implemented the assignment and/or copy constructor of your SpecialObject class properly.

@Hunger I thought QHash took a copy of objects when you insert them rather than using a reference to them as you are implying?

@ludde: Yes at that moment SpecialObject has got one QString and 5 qint32 attributes.
However, this is going to be developed and thus rising.

@ZapB: Thatswhy I wrote an own class for it, I know that I need special format for output purposes late on. And thatswhy I haven’t take “struct”.

Anyway, creating my object on the heap does not solve my problem either. During debugging I can see botch values in pDataController as on the screenshot above. And same CXX0030 error.

ZapB wrote:

Looks to me like you have not properly implemented the assignment and/or copy constructor of your SpecialObject class properly.

@Hunger I thought QHash took a copy of objects when you insert them rather than using a reference to them as you are implying?

Correct!

To quote from the docs about container classes [doc.qt.nokia.com]
The values stored in the various containers can be of any assignable data type. To qualify, a type must provide a default constructor, a copy constructor, and an assignment operator. This covers most data types you are likely to want to store in a container, including basic types such as int and double, pointer types, and Qt data types such as QString, QDate, and QTime, but it doesn’t cover QObject or any QObject subclass (QWidget, QDialog, QTimer, etc.). If you attempt to instantiate a QList<QWidget>, the compiler will complain that QWidget’s copy constructor and assignment operators are disabled. If you want to store these kinds of objects in a container, store them as pointers, for example as QList<QWidget *>.

And more important:

If we don’t provide a copy constructor or an assignment operator, C++ provides a default implementation that performs a member-by-member copy.

Theses autogenerated operators and constructors are most likely not sufficient!

Have you unit tested you SpecialObject class to ensure that it works properly for common operations (e.g. creation, destruction, assignment, copying, output)?

Can you post the code for SpecialObject please?

I think you will have to show us the SpecialObject class, if you cannot figure out what’s wrong with it from the help you’ve been given so far.

Even better, create a complete test case, consisting of just the class, a main method and a method that triggers the crash.

Here you have compileable but not yet linkable codes. LinkError see bottom.

DataItem.cpp

DataItem.h

DataController.cpp

DataController.h

MyDockWidget.cpp

MyDockWidget.h

I now get a Linker-Error:
1>Linking…
1>DataItem.obj : error LNK2019: unresolved external symbol “__declspec(dllimport) public: __thiscall QString::~QString(void)” (__imp_??1QString@@QAE@XZ) referenced in function __unwindfunclet$??0DataItem@@QAE@XZ$0

but I did not use any Libs or Dlls??! How is that be?

Yes you are. You are using the QtCore dll. Also where is your main() function?

You are missing the linker options in your pro file.
can you show it to us?
or what do you use for compiling?

For me, your code compiles fine.

Code looks OK to me. Except your DataController destructor should probably destroy the DataItems. But the way your DataItems are now, you should be able to pass them around by value, i.e. not bother with new/delete and the use of pointers.