all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Crashes on w32 and debugging
Date: Sat, 01 Mar 2008 09:56:57 +0000	[thread overview]
Message-ID: <47C92869.4000506@gnu.org> (raw)
In-Reply-To: <uejaukcd8.fsf@gnu.org>

Eli Zaretskii wrote:
> Jason, could it be that this "msg c113 not expected" thing is
> something to worry about?
>   

No. I've tracked these messages down to IME and third party extensions 
(such as virus scanners) that either broadcast or hook into every 
application and send messages from the RegisterWindowMessage range to 
themselves via any Window the application has created. I think this 
debugging statement can be disabled now, it is probably left over from 
early development when private messages were being created for Emacs' 
use and the developers wanted to double check that they were handling 
all the messages they had created.





  reply	other threads:[~2008-03-01  9:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28  8:30 Crashes on w32 and debugging Lennart Borgman (gmail)
2008-02-28  8:57 ` Jason Rumney
2008-02-29  0:30   ` Lennart Borgman (gmail)
2008-02-29  0:35     ` Jason Rumney
2008-02-29 21:59       ` Lennart Borgman (gmail)
2008-02-29 23:16         ` Jason Rumney
2008-02-29 23:21           ` Jason Rumney
2008-02-29 23:33             ` Lennart Borgman (gmail)
2008-03-01 10:43             ` Lennart Borgman (gmail)
2008-03-01 10:52               ` Lennart Borgman (gmail)
2008-03-01 20:43                 ` Kim F. Storm
2008-03-02  1:01                   ` Lennart Borgman (gmail)
2008-03-01  9:44         ` Eli Zaretskii
2008-03-01  9:56           ` Jason Rumney [this message]
2008-02-29  2:02     ` Stefan Monnier
2008-02-29 10:40       ` Eli Zaretskii
2008-02-29  9:51 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47C92869.4000506@gnu.org \
    --to=jasonr@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.