unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu)
Date: Sun, 12 Feb 2006 23:40:47 -0500	[thread overview]
Message-ID: <E1F8VW3-0007TA-Nz@fencepost.gnu.org> (raw)
In-Reply-To: <v9oe1hg44k.fsf@marauder.physik.uni-ulm.de> (message from Reiner Steib on Wed, 08 Feb 2006 18:19:23 +0100)

    > Please describe exactly what actions triggered the bug
    > and the precise symptoms of the bug:

    `<f1> k [Ctrl <tool-bar> <help>]'  (But it's not reproducible.)

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 182940272320 (LWP 4018)]
    x_catch_errors_unwind (dummy=9829361)
	at [...]/emacs/src/xterm.c:7530

The first question is, what was the immediate cause of the crash?
Could you please see what instruction crashed, and what data it was
looking at?

Maybe it was examining x_error_message->dpy.
What is the value of x_error_message?

       reply	other threads:[~2006-02-13  4:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v9oe1hg44k.fsf@marauder.physik.uni-ulm.de>
2006-02-13  4:40 ` Richard M. Stallman [this message]
2006-02-13 14:04   ` SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu) Reiner Steib
2006-02-13 17:05     ` Stefan Monnier
2006-02-14  0:40       ` Richard M. Stallman
2006-02-17 14:27       ` Reiner Steib
2006-02-17 15:20         ` Reproducible crashes: dropping an URL (was: SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu)) Reiner Steib
2006-02-17 16:01           ` Reproducible crashes: dropping an URL Stefan Monnier
2006-02-20 14:59             ` SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu) (was: Reproducible crashes: dropping an URL) Reiner Steib
2006-02-20 15:04               ` SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu) Stefan Monnier
2006-02-20 20:05                 ` Reiner Steib
2006-02-21  4:39                   ` Chong Yidong
2006-02-22  5:23                     ` Richard M. Stallman
2006-02-21  5:30                 ` Richard M. Stallman
2006-02-17 20:45           ` Reproducible crashes: dropping an URL (was: SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu)) Nick Roberts
2006-02-17  8:04 SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu) John W. Eaton
  -- strict thread matches above, loose matches on Subject: below --
2006-02-21 21:33 John W. Eaton
2006-02-23  2:39 ` Richard Stallman
2006-02-24  9:55 ` Richard Stallman
2006-02-25  7:45   ` John W. Eaton
2006-02-25 15:20     ` Chong Yidong
2006-02-25 15:36       ` Chong Yidong
2006-02-25 17:47         ` John W. Eaton
2006-02-25 23:29           ` Chong Yidong
2006-02-26  3:37             ` John W. Eaton
2006-02-27  8:58             ` Richard Stallman
2006-02-28  0:51               ` Chong Yidong
2006-03-05  0:59                 ` Richard Stallman
2006-02-26 16:00           ` Richard Stallman
2006-02-26 12:11         ` Richard Stallman

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=E1F8VW3-0007TA-Nz@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).