From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: 22526@debbugs.gnu.org, andrewjmoreton@gmail.com
Subject: bug#22526: 25.0.90; Crash starting gnus
Date: Sun, 14 Feb 2016 18:57:54 +0200 [thread overview]
Message-ID: <838u2nz0tp.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9PF3fm5jiz6hETBZOLw2ryKXpXTpDvN6GV+OvQ42HU5RA@mail.gmail.com> (message from Fabrice Popineau on Sun, 14 Feb 2016 10:05:12 +0100)
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Sun, 14 Feb 2016 10:05:12 +0100
> Cc: andrewjmoreton@gmail.com, 22526@debbugs.gnu.org
>
> Btw, what exactly is the difference between memInfo.BaseAddress and
> memInfo.AllocationBase? The MSDN documentation describes both using
> the same words in different order, so it's hard to understand.
>
> Same question here.
> Re-reading the documentation, I would understand it as :
> - BaseAddress is the adress that we passed to VirtualQuery, rounded down to the beginning of the page
> - AllocationBase is the start of the bloc of pages that we have committed previously.
> So we should use AllocationBase.
Right. Although running under a debugger seems to indicate that they
are always the same, somehow.
> Another thing I wonder: could pages be in a state MEM_RESERVE | MEM_COMMIT?
> I hope not.
No, these 2 states are mutually exclusive, according to my reading of
the documentation.
> > > The error codes from VirtualAlloc() here are crucial.
> >
> > The error is ERROR_INVALID_PARAMETER (87), as Andy just reported.
> >
> > Weird. There is a good chance that *var is wrong and you are right.
>
> Maybe. I'd actually expect ERROR_INVALID_ADDRESS in that case, but
> this is not explicitly documented anywhere.
>
>
> Something I refer to when I need to understand the inner workings of the win32 API is the source code for
> ReactOS:
> http://doxygen.reactos.org/d2/d2c/virtual_8c_a39ad5f8f1a5214f4874171695ab2bd6b.html#a39ad5f8f1a5214f4874171695ab2bd6b
>
> (for example).
> Not ideal, and it doesn't mean the MS thing works the same way, but at least it allows to understand some
> things.
Yes. There's also WINE.
next prev parent reply other threads:[~2016-02-14 16:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 22:13 bug#22526: 25.0.90; Crash starting gnus Andy Moreton
2016-02-07 5:42 ` Lars Ingebrigtsen
2016-02-07 16:00 ` Eli Zaretskii
2016-02-07 20:58 ` Andy Moreton
2016-02-07 21:05 ` Eli Zaretskii
2016-02-11 2:06 ` Andy Moreton
2016-02-11 20:27 ` Eli Zaretskii
2016-02-11 21:20 ` Andy Moreton
2016-02-11 21:26 ` Eli Zaretskii
2016-02-12 13:34 ` Andy Moreton
2016-02-12 16:16 ` Eli Zaretskii
2016-02-12 22:26 ` Andy Moreton
2016-02-13 8:28 ` Eli Zaretskii
2016-02-13 10:44 ` Eli Zaretskii
2016-02-13 16:08 ` Fabrice Popineau
2016-02-13 16:42 ` Eli Zaretskii
2016-02-13 21:35 ` Fabrice Popineau
2016-02-13 22:11 ` Eli Zaretskii
2016-02-13 23:44 ` Fabrice Popineau
2016-02-14 5:49 ` Eli Zaretskii
2016-02-14 9:05 ` Fabrice Popineau
2016-02-14 16:57 ` Eli Zaretskii [this message]
2016-02-14 5:41 ` Eli Zaretskii
2016-02-14 14:17 ` Andy Moreton
2016-02-14 16:55 ` Eli Zaretskii
2016-02-14 17:51 ` Eli Zaretskii
2016-02-14 21:04 ` Fabrice Popineau
2016-02-14 21:29 ` Eli Zaretskii
2016-02-14 21:31 ` Fabrice Popineau
2016-02-14 21:34 ` Eli Zaretskii
2016-02-14 21:41 ` Fabrice Popineau
2016-02-15 3:32 ` Eli Zaretskii
2016-02-15 8:09 ` Fabrice Popineau
2016-02-15 11:39 ` Eli Zaretskii
2016-02-13 15:16 ` Andy Moreton
2016-02-13 15:52 ` Eli Zaretskii
2016-02-13 21:26 ` Andy Moreton
2016-02-16 1:18 ` Andy Moreton
2016-02-16 3:46 ` Eli Zaretskii
2016-02-20 11:08 ` Eli Zaretskii
2016-02-20 16:17 ` Andy Moreton
2016-02-20 17:01 ` Eli Zaretskii
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=838u2nz0tp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22526@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=fabrice.popineau@gmail.com \
/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).