In the bug report case we’re throwing that error ourselves after a call to fopen() returns NULL. The only way to get error info for that (that I know of) is errno.
Cheers, Jeff. > On 13 Aug 2018, at 21:37, Nhat Khai <[email protected]> wrote: > > Hi Jeff, > Is the current code able to log all the exception from multiple thread into > a file with full track stack, and exception message? I think, if it is, I > don't think you need errno if the exception message are used in the correct > way - which should be a message with some information for debugging, and > where it come from. Exception really design to replace errno, and more rich > of information. > > On Mon, Aug 13, 2018 at 4:30 PM Jeff Young <[email protected] > <mailto:[email protected]>> wrote: > I’m putting in some more/better error messages to try and catch a file-save > issue some folks are having [1]. > > Is errno defined on MSW? > > Thanks, > Jeff. > > [1] https://bugs.launchpad.net/kicad/+bug/1786512 > <https://bugs.launchpad.net/kicad/+bug/1786512> > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : https://launchpad.net/~kicad-developers > <https://launchpad.net/~kicad-developers> > More help : https://help.launchpad.net/ListHelp > <https://help.launchpad.net/ListHelp> > > > -- > Nhat Khai Nguyen
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
