Weird problem with translate()

[Santosh Reddy]

This might be total unrelated observation - Storing QModelIndex is not a good idea, check the note from documentation, also hope you are not using QModelIndex _currentPatternIndex; (or any other pointer) before setting it up.

Note: Model indexes should be used immediately and then discarded. You should not rely on indexes to remain valid after calling model functions that change the structure of the model or delete items. If you need to keep a model index over time use a QPersistentModelIndex.

[romariorios]

This might be total unrelated observation - Storing QModelIndex is not a good idea, check the note from documentation,

QPersistentModelIndex was giving me some weird bugs that vanished when I started to use QModelIndex.

also hope you are not using QModelIndex _currentPatternIndex; (or any other pointer) before setting it up.

I'm pretty sure I'm not.

[Santosh Reddy]

the second backtrace posted is same as first one

[MarekR22]

1. title of topic is strange, it is almost not related to your problem. I would say proper title should be: "Class crushes when any new field is added"
2. this kind of problems usually are result of errors in other parts of code. Problem just manifest it self in this place. There can be couple reasons: dangling pointer, wrong type cast, binary compability break (when using dlls), or some compiler cached data not updated correctly (here point 4 will help).
3. I'm afraid that finding problem without having whole project will be quite hard
4. did you clean project (call "make clean" or rebuild project), sometimes it helps in such cases.

[romariorios]

1. title of topic is strange, it is almost not related to your problem. I would say proper title should be: "Class crushes when any new field is added"
2. this kind of problems usually are result of errors in other parts of code. Problem just manifest it self in this place. Problem just manifest it self in this place. There can be couple reasons: dangling pointer, wrong type cast, binary compability break (when using dlls), or some compiler cached data not updated correctly (here point 4 will help).
3. I'm afraid that finding problem without having whole project will be quite hard
4. did you clean project (call "make clean" or rebuild project), sometimes it helps in such cases.

1 - Noted, sorry about that. It is related to translate(), though.
2 - Well, it never happened before and how can it be in another part of the code if I don't even use the new field?
Still in 2, about the reasons:
- Dangling pointer: You mean, the newly added one? If that's so, it happens with any type, even with an int, so I don't know how that can be the problem.
- Wrong type cast: Again, if you mean the new field, it happens with any type.
- Binary compability break (when using dlls): I was on Windows before, but it also happens on Linux.
- Compiler cached data: I don't believe so and I'll tell you why in 4.
3 - As I am, as well
4 - It was one of the first things I tried, but it didn't help at all.

the second backtrace posted is same as first one

D'oh!

Here they are:
When I create the new field before _ui: http://pastebin.com/1jQF8X4u
When I create the new field after _ui and then use it somewhere in the code: http://pastebin.com/hJrG5CFf

[romariorios]

Well, just reporting again to say that the cause of the problem.

Some time ago, I changed the name of mainwindow.hpp to stimulatormainwindow.hpp, but I forgot to change the name of the #include in main.cpp and - I don't know why - to remove the old mainwindow.hpp. So, while I didn't change StimulatorMainWindow, it was fine, because the old mainwindow.hpp still remained valid.

But when I needed to change it for real - that is, now - the problem blew up in my face.

I feel dumb.

Anyway, thanks to everyone that tried to help.