Doesn't it look like the contents of that array?Originally Posted by taylor34
Do you use threads? Could you post the code which is run after the click?
Doesn't it look like the contents of that array?Originally Posted by taylor34
Do you use threads? Could you post the code which is run after the click?
The bus error on Solaris is sometimes caused by a bug in the compiler. Take that into consideration when looking for solutions.
That's what I was wondering, because where it breaks in the debugger is way down in some of the qt base files, way after the C baseline code has executed. It appears to die because it tries to do qlnode::getData() on an invalid widget address (the 0x1010101) that it gets from "it", some variable inside the qt baseline code.Originally Posted by wysota
Taylor34
Btw, found out the problem. When I was passing my button number down to lower legacy stuff, it was interpretting it as hex so 24 became 36, blowing out the boundaries of my boolean array. Now why it caused the qt stuff to blow up on the sun, I don't know--it blew up in the correct place on windows. At least this is here for future reference by someone.
Taylor34
Bookmarks