From: Eli Zaretskii <eliz@gnu.org>
To: dhruva <dhruvakm@gmail.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs (HEAD) crash on M$ (XP) built with MinGW
Date: Tue, 21 Oct 2008 10:30:43 +0200 [thread overview]
Message-ID: <uljwigxjg.fsf@gnu.org> (raw)
In-Reply-To: <e3f230850810210055w19b8acefr5a654715dce44a8a@mail.gmail.com>
> Date: Tue, 21 Oct 2008 13:25:38 +0530
> From: dhruva <dhruvakm@gmail.com>
> Cc: "Eli Zaretskii" <eliz@gnu.org>, emacs-devel@gnu.org
>
> > FWIW, I cannot reproduce it either.
> >
> >> If the fix is safe (defensive), IMHO we could get that in as I
> >> continue to debug by adding some extra code in the 'if' block.
> >
> > IMO is best to let it stand, or even add an assertion; the best way to
> > catch it is by having it happen.
I completely agree with Juanma: your ``defensive'' fix will simply
sweep the problem under the carpet, and it won't get fixed for a long
time, considering that no one can currently reproduce it except
yourself.
> Could we just log the required extra information for further debugging
> when that happens? Allowing it to crash is a serious inconvenience
> (especially for me since I use the code from HEAD for my regular
> work)
Then please help us debug and fix this ASAP. TIA
next prev parent reply other threads:[~2008-10-21 8:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 12:38 Emacs (HEAD) crash on M$ (XP) built with MinGW dhruva
2008-10-20 14:41 ` Eli Zaretskii
2008-10-21 3:42 ` dhruva
2008-10-21 5:40 ` dhruva
2008-10-21 5:58 ` dhruva
2008-10-21 6:38 ` Eli Zaretskii
2008-10-21 6:41 ` Eli Zaretskii
2008-10-21 7:11 ` dhruva
2008-10-21 7:41 ` Juanma Barranquero
2008-10-21 7:55 ` dhruva
2008-10-21 8:03 ` Juanma Barranquero
2008-10-21 8:30 ` Eli Zaretskii [this message]
2008-10-25 16:51 ` dhruva
2008-10-25 16:56 ` dhruva
2008-10-27 4:30 ` dhruva
2008-10-27 20:09 ` Eli Zaretskii
2008-10-28 4:00 ` dhruva
2008-10-28 8:20 ` Juanma Barranquero
2008-10-28 18:42 ` Eli Zaretskii
2008-10-29 2:28 ` Stephen J. Turnbull
2008-10-29 6:39 ` Werner LEMBERG
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=uljwigxjg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dhruvakm@gmail.com \
--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 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.