From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu)
Date: Mon, 20 Feb 2006 10:04:47 -0500 [thread overview]
Message-ID: <jwvy8065ax8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <v9accmjctw.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 20 Feb 2006 15:59:23 +0100")
> I recompiled with this change on 2006-02-17. I can't reproduce the
> Drag/drop crash anymore.
Good.
> Today I got another "x_error_message == 0x0" crash:
> --8<---------------cut here---------------start------------->8---
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000000004fe8b0 in x_catch_errors_unwind (dummy=20426868)
> at [...]/emacs/src/xterm.c:7543
> warning: Source file is more recent than executable.
> 7543 Display *dpy = x_error_message->dpy;
> (gdb) bt full
> #0 0x00000000004fe8b0 in x_catch_errors_unwind (dummy=20426868)
> at [...]/emacs/src/xterm.c:7543
> dpy = Variable "dpy" is not available.
> (gdb) xbacktrace
> (gdb) p x_error_message
> $1 = (struct x_error_message_stack *) 0x0
> (gdb)
> --8<---------------cut here---------------end--------------->8---
What's the C backtrace?
Stefan
next prev parent reply other threads:[~2006-02-20 15:04 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 ` SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu) Richard M. Stallman
2006-02-13 14:04 ` 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 ` Stefan Monnier [this message]
2006-02-20 20:05 ` SEGV in x_catch_errors_unwind (x86_64-unknown-linux-gnu) 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=jwvy8065ax8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
/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).