taylor34
15th February 2006, 15:38
Hey--
Working on a sun workstation with qt 3.3, I've been getting a random bus error from one of my gui's. I've got a list of 32 buttons, basically clicking the button activates a boolean in an array stored off in some legacy C code. If I switch the checkbox buttons around to activate all 32 at one time, there's no problem. However, just doing it one by one causes it to blow up at some point between 2 and 20 clicks. I deleted all the buttons and redid them, doesn't help. Making the array of 32 booleans in the legacy C code integers only makes the issue worse (1 to 5 clicks to blow up instead of 2 to 20). It definitely has something to do with that array, but doesn't really make any sense why that should be causing the QT stuff to blow up. From the debugger, it appears as though one of the widgets may acquire an invalid address (0x1010101) at some point. Any suggestions? I'm going to try and run it under windows to see if that makes a difference too. Thanks!
Taylor34
Working on a sun workstation with qt 3.3, I've been getting a random bus error from one of my gui's. I've got a list of 32 buttons, basically clicking the button activates a boolean in an array stored off in some legacy C code. If I switch the checkbox buttons around to activate all 32 at one time, there's no problem. However, just doing it one by one causes it to blow up at some point between 2 and 20 clicks. I deleted all the buttons and redid them, doesn't help. Making the array of 32 booleans in the legacy C code integers only makes the issue worse (1 to 5 clicks to blow up instead of 2 to 20). It definitely has something to do with that array, but doesn't really make any sense why that should be causing the QT stuff to blow up. From the debugger, it appears as though one of the widgets may acquire an invalid address (0x1010101) at some point. Any suggestions? I'm going to try and run it under windows to see if that makes a difference too. Thanks!
Taylor34