unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@supelec.fr>
Cc: lekktu@gmail.com, 12544@debbugs.gnu.org
Subject: bug#12544: -r110296..110297 causes random crashes in optimized build on Windows
Date: Mon, 01 Oct 2012 13:41:44 +0200	[thread overview]
Message-ID: <83626uctc7.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9N8VqO24Ds+Spkg3OzQdr3YvkKiBQGHmyZOCrAZmk3BAA@mail.gmail.com>

> From: Fabrice Popineau <fabrice.popineau@supelec.fr>
> Date: Mon, 1 Oct 2012 13:32:13 +0200
> Cc: lekktu@gmail.com, 12544@debbugs.gnu.org
> 
> > I think I fixed this in trunk revision 110318.  The problem was that
> > the call to term_ntproc, as part of shutting down Emacs, deleted the
> > critical sections used by the timer threads and by setitimer, so any
> > call to setitimer after that would use an invalid critical section
> > object.  I now make sure any calls to setitimer after deleting the
> > critical sections will return immediately without doing anything.
> >
> >
> The explanation seems fine. The experimentation too : I did a bootstrap
> (64bits full optimization). It ran smoothly.

Great, thanks for testing.





  reply	other threads:[~2012-10-01 11:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  1:36 bug#12544: -r110296..110297 causes random crashes in optimized build on Windows Juanma Barranquero
2012-10-01  7:31 ` Fabrice Popineau
2012-10-01  8:12   ` Eli Zaretskii
2012-10-01  9:34     ` Eli Zaretskii
2012-10-01 11:32       ` Fabrice Popineau
2012-10-01 11:41         ` Eli Zaretskii [this message]
2012-10-01  8:37 ` Eli Zaretskii
2012-10-01  9:47   ` Eli Zaretskii
2012-10-01 11:45   ` Juanma Barranquero
2012-10-01 12:30     ` Eli Zaretskii
2012-10-01 14:28       ` Juanma Barranquero
2012-10-01 14:52         ` Eli Zaretskii
2012-10-01 14:58           ` Fabrice Popineau
2012-10-01 11:41 ` 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=83626uctc7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12544@debbugs.gnu.org \
    --cc=fabrice.popineau@supelec.fr \
    --cc=lekktu@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).