John,
please stay on topic and and only that.
Michael
Thanks for the extra info.
I haven't gotten to the crash code yet. The crash happens much later than I expected, so I set a breakpoint at what seems to be the guilty function, which I call Play(). It handles init of a channel and starts playback. BUT ...
I'm dealing with another issue: the debug module is enforcing assignment of the error code to a variable in the INI_SETKEY command. That is, it throws an "expecting a =" error. I assume that means I have to reform those lines to
local succeed as dword
succeed = INI_SETKEY(blah blah blah)
Only debug in 1.9.7.0 enforces this. I know that it's good practice to check these sorts of actions, but I think this requirement is excessive.
But anyway, I'll fix it and eventually get to my crash condition.
John,
please stay on topic and and only that.
Michael
John, no offense, but I don't understand any part of your comment.
My issues only appear in Beta 1.9.7.0, so naturally I thought this was the place to discuss them. But in any case, Rene told me enough to help me.
INI_SetKey takes an optional default-value-parameter - if this line in your code already has parenthesis around the parameters you might check the codeline directly above this - I can imagine there's another call to some function that takes an optional parameter so the line you want to change is not the one that causes the error- but the line above...
Where are my manners? Welcome and Happy Coding!
I think there are missing some Forum-sections as beta-testing and support
If the code is not private, you could upload it here and I could check the possible cause of error.
Petr
Learn 3D graphics with ThinBASIC, learn TBGL!
Windows 10 64bit - Intel Core i5-3350P @ 3.1GHz - 16 GB RAM - NVIDIA GeForce GTX 1050 Ti 4GB
Sorry guys, a lot has happened in my life and I forgot about this thread.
I finally found the cause. I was calling a function and assigning its value like this:
x = my_function
when the proper syntax is:
call my_function to x
After I changed my code, my program runs fine in all of the more recent versions of thinBasic. For some reason the older version accepted and used my original syntax without any errors.
Thanks for the help.
x = my_function should be absolutely valid.
Can you please post a little bit more of your not working code?
Or create a little script reproducing the problem?
I need to see how my_function is declared.
Thanks a lot
Eros
www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000
Ah, interesting. Man, I hope I didn't change hundreds of function calls for no good reason. (My media player is over 12,000 lines of code.)
Okay, thanks, I'll find a section that I can use for a sample script and post it here. It might take a day or so.
I apologize, Eros, I can't replicate the crashes. I'm completely baffled. I must have fixed the real problem without realizing it.
To clarify, older versions of my program still crash in all of the betas. It's not something I imagined.
To try to replicate the crashes, I used a newer version and changed the function calls back to "x = my_function." It's this version that doesn't seem to crash on the function calls. I changed something to fix that issue, apparently.
Bookmarks