Re: sysError values...
Here is another place for MacOS system errors: https://www.macheat.com/general-error-codes-for-os-x most probably doesn't list all errors... Thierry Douez sunny-tdz.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
Is it 13 or -13? I didn't see an entry for -13, but negative errors are different. Also this may not be a complete list, or the sysError() function in LC may not have anything to do with *actual* OS X system errors, and finally you may be getting the actual last error the OS generated, but it has nothing to do with your problem. Bob S > On Jan 29, 2019, at 17:16 , Paul Dupuis via use-livecode > wrote: > > So thanks for finding this. I was Googling things like "Livecode list of > system errors" or "LiveCode sysError value list" and so on. I was hoping or > thinking LiveCode might have a FAQ or some document on their website listing > them. > > That said, I am not sure this page actually represents the values returned by > the sysError() function in LiveCode. First of all it list two different > errors with code "13": > > dsIrqErr = 13, /*uninstalled interrupt error*/ > sdmPRAMInitErr = 13, /*Slot PRAM could not be initialized.*/ > > Neither errors make much sense in the context of where in the script this > error is occurring. The script is attempting to write a file and it is > failing. I am 99% certain this issue is a permission issue (no write access > to the folder). However, have the exact and correct error message > corresponding to the sysError() function returning a value of 13 would be > nice to help troubleshoot. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
Thank you Trevor! On 1/30/2019 8:57 AM, Trevor DeVore via use-livecode wrote: On Wed, Jan 30, 2019 at 7:11 AM Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: But absolutely no mention of where the OSX sysError value comes from. For Linux and Windows you can do a targeted search and find information. It was easy to find https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes (even if there is 15999 codes!) I think that sysError() on macOS is just returning the OSErr or OSStatus codes returned by macOS API calls. I found this document on error handling which is informative: https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ErrorHandlingCocoa/ErrorObjectsDomains/ErrorObjectsDomains.html#//apple_ref/doc/uid/TP40001806-CH202-CJBGAIBJ While the document discusses NSError (Cocoa) it does bring up the concept of domains. In Listing 1-1 it lists the POSIX domain errors with "13" being a "Permission Denied" error. Table 1-1 lists the various domains with information on which header files contain the error codes. I searched the non-Cocoa headers on opensource.apple.com and found these urls: https://opensource.apple.com/source/xnu/xnu-792/osfmk/mach/kern_return.h https://opensource.apple.com/source/xnu/xnu-4570.71.2/bsd/sys/errno.h.auto.html https://opensource.apple.com/source/CarbonHeaders/CarbonHeaders-18.1/MacErrors.h ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
On Wed, Jan 30, 2019 at 7:11 AM Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: > > But absolutely no mention of where the OSX sysError value comes from. > For Linux and Windows you can do a targeted search and find information. > It was easy to find > https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes > (even if there is 15999 codes!) > I think that sysError() on macOS is just returning the OSErr or OSStatus codes returned by macOS API calls. I found this document on error handling which is informative: https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ErrorHandlingCocoa/ErrorObjectsDomains/ErrorObjectsDomains.html#//apple_ref/doc/uid/TP40001806-CH202-CJBGAIBJ While the document discusses NSError (Cocoa) it does bring up the concept of domains. In Listing 1-1 it lists the POSIX domain errors with "13" being a "Permission Denied" error. Table 1-1 lists the various domains with information on which header files contain the error codes. I searched the non-Cocoa headers on opensource.apple.com and found these urls: https://opensource.apple.com/source/xnu/xnu-792/osfmk/mach/kern_return.h https://opensource.apple.com/source/xnu/xnu-4570.71.2/bsd/sys/errno.h.auto.html https://opensource.apple.com/source/CarbonHeaders/CarbonHeaders-18.1/MacErrors.h -- Trevor DeVore ScreenSteps www.screensteps.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
On 1/29/2019 7:03 PM, Paul Dupuis via use-livecode wrote: In general, where does one find the English equivalent of the number returned by sysError for a given OS? In this specific case, the OS is OSX and the value is 13. Richard: I completely agree. Apple is seemingly the worst in this regard. Especially considering the LC Dictionary entry for sysError where it states: On Unix systems, thesysErrorfunctionreturnsthevalueof the "errno"variable. On Windows systems, thesysErrorfunctionreturnsthevaluereturned by the "GetLastError()"function. But absolutely no mention of where the OSX sysError value comes from. For Linux and Windows you can do a targeted search and find information. It was easy to find https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes (even if there is 15999 codes!) If someone form LiveCode can tell me where the OSX sysError value actually comes from, I will try to (a) find an authoritative list and (b) finally learn enough of GIT to update the dictionary entry for sysError Rick: Thank you for the confirmation that it is a permissions issue. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
Hi Paul, I have gone down that road before too. Yes, sysError 13 is a permissions error. Rick > On Jan 29, 2019, at 8:16 PM, Paul Dupuis via use-livecode > wrote: > > So thanks for finding this. I was Googling things like "Livecode list of > system errors" or "LiveCode sysError value list" and so on. I was hoping or > thinking LiveCode might have a FAQ or some document on their website listing > them. > > That said, I am not sure this page actually represents the values returned by > the sysError() function in LiveCode. First of all it list two different > errors with code "13": > > dsIrqErr = 13, /*uninstalled interrupt error*/ > sdmPRAMInitErr = 13, /*Slot PRAM could not be initialized.*/ > > Neither errors make much sense in the context of where in the script this > error is occurring. The script is attempting to write a file and it is > failing. I am 99% certain this issue is a permission issue (no write access > to the folder). However, have the exact and correct error message > corresponding to the sysError() function returning a value of 13 would be > nice to help troubleshoot. > > > > On 1/29/2019 7:18 PM, Bob Sneidar via use-livecode wrote: >> dsIrqErr = 13, /*uninstalled interrupt error*/ >> >> http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/ >> >> I just googled it. Google is a search engine where you type in words into a >> field on a web page that have something to do with what you want to know and >> then the search engine >> >> NVM. :-P >> >> Bob S >> >> >>> On Jan 29, 2019, at 16:03 , Paul Dupuis via use-livecode >>> wrote: >>> >>> In general, where does one find the English equivalent of the number >>> returned by sysError for a given OS? >>> >>> In this specific case, the OS is OSX and the value is 13. >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
On 1/29/19 7:10 PM, Richard Gaskin via use-livecode wrote: I wish Apple well, but I'm finding myself feeling hopeful as a result of their sales/stock drop. The best years of their relations with developers were when they were hungry, in the mid-90s. Hunger is tonifying. Maybe another six months of decline and they'll start remember that it's app devs who make a platform worth using. Apple appears a bit unclear on the concept...from an AP story: "Apple hoped to offset slowing demand for iPhones by raising the prices of its most important product..." -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
Paul Dupuis wrote: > I was Googling things like "Livecode list of system errors" or > "LiveCode sysError value list" and so on. I was hoping or thinking > LiveCode might have a FAQ or some document on their website > listing them. > > That said, I am not sure this page actually represents the values > returned by the sysError() function in LiveCode. First of all it list > two different errors with code "13"... And now you've discovered by LiveCode doesn't attempt to document OS error codes: If the OS vendor themselves can't keep it straight, how could any third party? :) I wish Apple well, but I'm finding myself feeling hopeful as a result of their sales/stock drop. The best years of their relations with developers were when they were hungry, in the mid-90s. Hunger is tonifying. Maybe another six months of decline and they'll start remember that it's app devs who make a platform worth using. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
So thanks for finding this. I was Googling things like "Livecode list of system errors" or "LiveCode sysError value list" and so on. I was hoping or thinking LiveCode might have a FAQ or some document on their website listing them. That said, I am not sure this page actually represents the values returned by the sysError() function in LiveCode. First of all it list two different errors with code "13": dsIrqErr = 13, /*uninstalled interrupt error*/ sdmPRAMInitErr = 13, /*Slot PRAM could not be initialized.*/ Neither errors make much sense in the context of where in the script this error is occurring. The script is attempting to write a file and it is failing. I am 99% certain this issue is a permission issue (no write access to the folder). However, have the exact and correct error message corresponding to the sysError() function returning a value of 13 would be nice to help troubleshoot. On 1/29/2019 7:18 PM, Bob Sneidar via use-livecode wrote: dsIrqErr = 13, /*uninstalled interrupt error*/ http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/ I just googled it. Google is a search engine where you type in words into a field on a web page that have something to do with what you want to know and then the search engine NVM. :-P Bob S On Jan 29, 2019, at 16:03 , Paul Dupuis via use-livecode wrote: In general, where does one find the English equivalent of the number returned by sysError for a given OS? In this specific case, the OS is OSX and the value is 13. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: sysError values...
dsIrqErr = 13, /*uninstalled interrupt error*/ http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/ I just googled it. Google is a search engine where you type in words into a field on a web page that have something to do with what you want to know and then the search engine NVM. :-P Bob S > On Jan 29, 2019, at 16:03 , Paul Dupuis via use-livecode > wrote: > > In general, where does one find the English equivalent of the number returned > by sysError for a given OS? > > In this specific case, the OS is OSX and the value is 13. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
sysError values...
In general, where does one find the English equivalent of the number returned by sysError for a given OS? In this specific case, the OS is OSX and the value is 13. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
