all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: Re: End of file while generating loaddefs.el
Date: Fri, 20 Nov 2015 10:46:55 +0100	[thread overview]
Message-ID: <87y4dt3svk.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83egfl6p6a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Nov 2015 10:38:37 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 20 Nov 2015 09:23:10 +0100
>> From: martin rudalics <rudalics@gmx.at>
>> Cc: emacs-devel@gnu.org
>> 
>>  > into the GDB command to run Emacs, right after
>>  > the "run" part.  Then wait until it segfaults.
>> 
>> When I do that it doesn't segfault but simply produces the "End of file
>> during parsing" message you reported earlier.
>
> Darn!  Another memory-related Heisenbug!
>
> I guess the only way to debug this is see what happens inside prin1.
> AFAIR, it uses a temporary buffer to produce the string, so this might
> be due to GC or something.

For the record: if it weren't on Windows, you could say something like

ulimit -c unlimited  # Possibly a bad idea on 64bit systems

and then run the program again from the command line.  This should make
it behave identically until crashing, producing a "core" file when doing
so.

You can then run

gdb src/emacs core   # or whatever your corresponding binary was

and then do a post-mortem debug, particularly looking at the backtrace.

-- 
David Kastrup



  reply	other threads:[~2015-11-20  9:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 17:40 End of file while generating loaddefs.el Eli Zaretskii
2015-11-18  7:50 ` martin rudalics
2015-11-18 17:29   ` Eli Zaretskii
2015-11-19  8:13     ` martin rudalics
2015-11-19 16:15       ` Eli Zaretskii
2015-11-19 16:33         ` John Wiegley
2015-11-20  8:23         ` martin rudalics
2015-11-20  8:38           ` Eli Zaretskii
2015-11-20  9:46             ` David Kastrup [this message]
2015-11-20 14:50               ` Eli Zaretskii
2015-11-20 21:10             ` Eli Zaretskii
2015-11-21  8:33               ` martin rudalics
2015-11-21  8:49                 ` Eli Zaretskii
2015-11-21 11:23                   ` martin rudalics
2015-11-21 11:33                     ` David Kastrup
2015-11-21 11:59                       ` Eli Zaretskii
2015-11-21 11:57                     ` Eli Zaretskii
2015-11-21 15:29                     ` 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

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

  git send-email \
    --in-reply-to=87y4dt3svk.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.