From: David Kastrup <dak@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: emacs-pretest-bug@gnu.org, Leo <sdl.web@gmail.com>
Subject: Re: 23.0.50; Emacs seg fault
Date: Sun, 30 Sep 2007 13:07:10 +0200 [thread overview]
Message-ID: <854phc5s4h.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87abr4a0nv.fsf@kfs-lx.testafd.dk> (Kim F. Storm's message of "Sun\, 30 Sep 2007 12\:49\:08 +0200")
storm@cua.dk (Kim F. Storm) writes:
> Leo <sdl.web@gmail.com> writes:
>
>> #1 0x08194676 in wait_reading_process_output (time_limit=30, microsecs=0, read_kbd=-1, do_display=1, wait_for_cell=137551137,
>> wait_proc=0x0, just_wait_proc=0) at process.c:4880
>
> I doubt that is the right line number due to compiler optimizations.
> Compile with CFLAGS="-g -O0" to get max debugging info.
From etc/DEBUG:
** When you are trying to analyze failed assertions, it will be
essential to compile Emacs either completely without optimizations or
at least (when using GCC) with the -fno-crossjumping option. Failure
to do so may make the compiler recycle the same abort call for all
assertions in a given function, rendering the stack backtrace useless
for identifying the specific failed assertion.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-09-30 11:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 21:10 23.0.50; Emacs seg fault Leo
2007-09-30 2:56 ` Stefan Monnier
2007-09-30 6:09 ` Leo
2007-09-30 12:55 ` Richard Stallman
2007-09-30 10:49 ` Kim F. Storm
2007-09-30 11:07 ` David Kastrup [this message]
2007-09-30 15:44 ` Leo
2007-10-01 17:41 ` Richard Stallman
2007-10-05 19:29 ` Leo
2007-09-30 16:10 ` Eli Zaretskii
2007-10-05 19:28 ` Leo
2007-10-06 22:41 ` Kim F. Storm
2007-10-07 7:34 ` Leo
2007-10-07 21:35 ` Kim F. Storm
2007-10-08 0:19 ` Leo
2007-10-08 13:01 ` Kim F. Storm
2007-10-08 16:09 ` Dan Nicolaescu
2007-10-08 19:13 ` Leo
2007-10-08 20:15 ` Dan Nicolaescu
2007-10-10 5:54 ` Leo
2007-10-10 8:08 ` Dan Nicolaescu
2007-10-10 9:35 ` Leo
2007-10-10 23:53 ` Dan Nicolaescu
2007-10-11 17:31 ` Leo
2007-10-11 21:31 ` Dan Nicolaescu
2007-10-10 5:59 ` Leo
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=854phc5s4h.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=sdl.web@gmail.com \
--cc=storm@cua.dk \
/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).