unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Babylon crashes Emacs
Date: Sat, 23 Jun 2007 16:42:42 +0300	[thread overview]
Message-ID: <uabuqpz1p.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0706230624u50ddfeaeja8ac4efb8237166f@mail.gmail.com> (lekktu@gmail.com)

> Date: Sat, 23 Jun 2007 15:24:44 +0200
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> On 6/23/07, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > The backtrace produced by DrMinGW (attached below) seems to indicate
> > that we get a WM_PAINT message that we somehow cannot grok(?).  Is it
> > possible that Babylon sends us WM_PAINT so that we draw some part of
> > our screen in a DC that isn't ours?
> 
> I get this backtrace.

Thanks.  I'm no longer sure that my assumption about WM_PAINT was
correct.  I don't have Babylon where I'm typing this, so how about if
you try to see what message(s) Babylon sends us?  For example, using
Winspector (http://www.windows-spy.com/).

> (BTW, how do you set drmingw to get such detailed backtrace?)

I don't see that my backtrace is more detailed than yours.  Note that
in your case we are deep inside system DLLs, where debug info is not
available.  For our functions, you get all the arguments and the
current line, AFAICS.  Am I missing something?

Anyway, the only gotcha with DrMinGW I know of is that the program
must be built with -gstabs, as it seems not to support DWARF-2 right
now.

  reply	other threads:[~2007-06-23 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23 12:33 Babylon crashes Emacs Eli Zaretskii
2007-06-23 13:24 ` Juanma Barranquero
2007-06-23 13:42   ` Eli Zaretskii [this message]
2007-06-24 16:59     ` 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=uabuqpz1p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).