Page 1 of 1
[SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 4:15 pm
by Randy Walker
This link should (I think) take you straight to the problem I encountered:
viewtopic.php?p=628812&hilit:#p628812
People wonder why I don't "upgrade". Still favor 5.40 for most things because I try 6.xx x64 and some things just don't work any more.
Re: Is it a bug or is it me (again) ?
Posted: Sun Oct 06, 2024 4:51 pm
by Paul
It's you
If you follow the changes made to latest versions of PB and follow the forum, you will try changing all types of ".l" to ".i" and the code will then work.
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 5:54 pm
by Randy Walker
Ok then. What other changes can cause the message:?
"The Debugged Executable Quit Unexpectedly"
I cannot compile my main project in 6,12 because I get that error.
I have converted all the .L variables to be .i so it's not that.
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 6:14 pm
by infratec
The code works here in PB 6.12 x86 asm backend on Win10 x64
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 6:15 pm
by Paul
The code you linked to compiles and executes fine with the type changes.
Outside of that, you would have to post more code to track other issues.
I am assuming you are compiling with 64bit version of PB. Have you tried compiling your code with 32bit version?
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 6:55 pm
by Randy Walker
Paul wrote: Sun Oct 06, 2024 6:15 pm
. . . you would have to post more code to track other issues.
I am assuming you are compiling with 64bit version of PB. Have you tried compiling your code with 32bit version?
Good assumption -- I am trying to compile on 64 bit PB in anticipation of MS discarding 32 bit support. So 32 bit option would be pointless. Afraid I am unable to share code from my main project as it would expose too much sensitive data entrusted to the company I used to work for. Some say it won't happen any time soon but could be Win 12 will drop it completely and without notice. Shtting on users is standard operating procedure for Microsoft as you probably well know.
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 9:37 pm
by Randy Walker
New Info -- I used calldebugger and [Step] to locate the offending line causing the crash.
Code: Select all
UserPick5 = ComboBoxGadget(#UserPick_5, 31, 0, 159, 20, #PB_ComboBox_UpperCase)
Of course I checked values on those 2 constants:
#UserPick_5 =320
#PB_ComboBox_UpperCase = 8192
Nothing jumping out at me in anything there.
UserPick5 value is of course unavailable because of the crash.
So is it a bug, or is it still me?
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 9:46 pm
by ChrisR
It's not you
There is a
Bug of the ComboboxGadget() with #PB_ComboBox_LowerCase or UpperCase in PB 6.12
Re: [SOLVED] Is it a bug or is it me (again) ? (it was me)
Posted: Sun Oct 06, 2024 9:50 pm
by Randy Walker
Me thinks it's a bug just like ChrisR said.
I found a bug report regarding same issue on ComboBoxGadget so I removed the #PB_ComboBox_UpperCase and I can compile without crashing now.
THANKS ChrisR !!!!
Suppose I should mention the issue I encountered was using PB v6.12x64 running on Win 11 Pro.
Re: Is it a bug or is it me (again) ?
Posted: Mon Oct 07, 2024 1:52 am
by BarryG
Paul wrote: Sun Oct 06, 2024 4:51 pmyou will try changing all types of ".l" to ".i" and the code will then work.
This is not a cure-all, though. Some structure types have to remain as ".l" to work. You can't just do a search/replace on them all.
Re: Is it a bug or is it me (again) ?
Posted: Mon Oct 07, 2024 4:11 am
by Paul
BarryG wrote: Mon Oct 07, 2024 1:52 am
Paul wrote: Sun Oct 06, 2024 4:51 pmyou will try changing all types of ".l" to ".i" and the code will then work.
This is not a cure-all, though. Some structure types have to remain as ".l" to work. You can't just do a search/replace on them all.
Exactly, which is why I said
The code you linked to compiles and executes fine with the type changes.
Outside of that, you would have to post more code to track other issues.
Also note if your code compiles fine in 32bit but fails in 64bit, there are most likely Types that need adjusting somewhere.