From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, bug-gnu-emacs@gnu.org
Subject: Re: Crash using text property 'composite on w32
Date: Tue, 12 Jun 2007 12:28:27 +0200 [thread overview]
Message-ID: <466E754B.8080201@gmail.com> (raw)
In-Reply-To: <u7iq9kgg8.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Tue, 12 Jun 2007 02:30:23 +0200
>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
>> Cc: bug-gnu-emacs@gnu.org
>>
>> Juanma Barranquero wrote:
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x010c798a in run_composition_function (from=267, to=269, prop=520)
>>> at composite.c:456
>>> 456 func = COMPOSITION_MODIFICATION_FUNC (prop);
>>> (gdb) bt
>>> #0 0x010c798a in run_composition_function (from=267, to=269, prop=520)
>>> at composite.c:456
>> Ah, thanks. I am not familiar with gdb.
>
> You could also configure drmingw.exe (from mingw-utils-0.3.tar.gz) as
> your JIT debugger. This is what I get from it if I try your recipe:
Thanks Eli. I have not noticed there is such a thing as drmingw before.
For those interested in downloading: This file is on the MinGW download
page. Many of the other files should be downloaded from SourceForge. It
seems like no one has had the time and interest to clean up the MinGW
download page yet.
next prev parent reply other threads:[~2007-06-12 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 16:32 Crash using text property 'composite on w32 Lennart Borgman (gmail)
2007-06-11 23:49 ` Jason Rumney
2007-06-11 23:58 ` Lennart Borgman (gmail)
2007-06-12 0:04 ` Jason Rumney
2007-06-12 0:07 ` Juanma Barranquero
2007-06-12 0:30 ` Lennart Borgman (gmail)
2007-06-12 3:19 ` Eli Zaretskii
2007-06-12 10:28 ` Lennart Borgman (gmail) [this message]
2007-06-12 15:44 ` Chong Yidong
2007-06-14 12:32 ` Kenichi Handa
2007-06-14 12:42 ` Lennart Borgman (gmail)
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=466E754B.8080201@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=eliz@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 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.