From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: gnutls on mingw64
Date: Fri, 29 Nov 2019 09:17:42 +0200 [thread overview]
Message-ID: <83eexrp2w9.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ohKTYjVh1ZsxOX7pguvEFDW51qeS8L67MVi+2p8gca1Zg@mail.gmail.com> (message from Richard Copley on Thu, 28 Nov 2019 22:22:16 +0000)
> From: Richard Copley <rcopley@gmail.com>
> Date: Thu, 28 Nov 2019 22:22:16 +0000
> Cc: emacs-devel <emacs-devel@gnu.org>
>
> GetLastError() is just an integer, like errno. You must have to do a little more work to get descriptive errors
> from other systems? There's probably an equivalent. The Application error log in Event Viewer springs to
> mind.
I usually do from the shell prompt:
net helpmsg NNN
where NNN is the code returned by GetLastError. (Programmatically,
there's the FormatMessage function to return the error string.)
Example:
D:\usr\eli>net helpmsg 2
The system cannot find the file specified.
> ("Dependencies" gets detailed information somehow. But for all I know (I haven't looked) it emulates the
> loader to see what happens.)
You can do the same with objdump, btw.
next prev parent reply other threads:[~2019-11-29 7:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:34 gnutls on mingw64 Stephen Leake
2019-11-26 15:42 ` Richard Copley
2019-11-27 1:10 ` Stephen Leake
2019-11-27 8:56 ` Richard Copley
2019-11-27 9:58 ` Stephen Leake
2019-11-26 15:46 ` Eli Zaretskii
2019-11-27 10:00 ` Stephen Leake
2019-11-27 15:53 ` Eli Zaretskii
2019-11-28 18:00 ` Stephen Leake
2019-11-28 22:22 ` Richard Copley
2019-11-29 7:17 ` Eli Zaretskii [this message]
2019-11-29 8:32 ` Richard Copley
2019-11-29 10:24 ` Eli Zaretskii
2019-11-29 3:16 ` Juanma Barranquero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eexrp2w9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rcopley@gmail.com \
--cc=stephen_leake@stephe-leake.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).