Your issue is something that may be worth looking into more thoroughly.
There is no technical reason why a 32-bit process shouldn't be able to run a 64-bit process. Indeed, Process Explorer does just that, every single time you launch it on a 64-bit system. Firefox is a strictly 32-bit application, too, and it does not fail to launch applications to open media.
Which means there are 3 possible reasons:
- You just fucked up ---> can be ruled out rather safely if the exact same backtick that didn't work before works now
- Code::Blocks has a bug, probably uninitialized variable, somewhere in ExpandTicks ---> that'd be a rather serious defect that would need fixing
- wxExecute not only sucks notoriously, but indeed has a bug that triggers randomly in this scenario ---> not ours to fix, but still important, and should be reported upstream
I can confirm that a 32bit process (Code::Blocks) can run a 64bit process, it works now....
almost all of the time. When I set up initially on a new computer I tend to have startup trouble, but after that it seems to work consistently.
I would not rule out the first bullet, I do that all the time
, but yes it is the same backtick.
Somehow it feels like something needs to be cached in somewhere before it becomes reliable (just a hunch). Perhaps that is wxExecute misbehaving sometimes.
More later.
