unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 16615-done@debbugs.gnu.org
Subject: bug#16615: 24.3.50; Fatal error visiting a directory (same as #16132?)
Date: Sun, 02 Feb 2014 05:41:15 +0200	[thread overview]
Message-ID: <83lhxu41wk.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ogTScy9j_StuTVwY6_xEiD27mi4=t8_kwJcBbOCuVpxZw@mail.gmail.com>

> Date: Sat, 1 Feb 2014 21:52:07 +0000
> From: Richard Copley <rcopley@gmail.com>
> Cc: 16615@debbugs.gnu.org
> 
> On 1 February 2014 20:43, Richard Copley <rcopley@gmail.com> wrote:
> >On 1 February 2014 20:12, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Please try the latest trunk and see if its solves the problem.
> > Seems fixed, many thanks. I should rebuild with the libraries enabled to be sure. I will let you know the result.
> 
> Yes, still fixed. Thanks again.

Thanks, closing.

(It's amazing how long such a glaring mistake can go unnoticed:
omitting WINAPI from the function pointer declaration means that the
compiler uses the wrong calling convention for it -- cdecl instead of
stdcall -- which explains both the crash and the smashed stack that
prevented you from obtaining a useful backtrace.  This code was there
since 14 years ago.)





  reply	other threads:[~2014-02-02  3:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 17:32 bug#16615: 24.3.50; Fatal error visiting a directory (same as #16132?) Richard Copley
2014-02-01 18:11 ` Eli Zaretskii
2014-02-01 19:09   ` Richard Copley
2014-02-01 19:34     ` Richard Copley
2014-02-01 20:05       ` Richard Copley
2014-02-01 20:12       ` Eli Zaretskii
2014-02-01 20:43         ` Richard Copley
2014-02-01 21:52           ` Richard Copley
2014-02-02  3:41             ` Eli Zaretskii [this message]
2014-02-01 22:48           ` Juanma Barranquero
2014-02-01 23:03             ` Richard Copley
2014-02-01 23:18               ` Juanma Barranquero
2014-02-01 23:24                 ` Richard Copley
2014-02-01 23:33                   ` 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=83lhxu41wk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16615-done@debbugs.gnu.org \
    --cc=rcopley@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).